Michael Nitschinger created MSHADE-216:
------------------------------------------
Summary: Relocation exclusion pattern ignored
Key: MSHADE-216
URL: https://issues.apache.org/jira/browse/MSHADE-216
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Michael Nitschinger
Hi,
I got a weird issue, maybe this is a bug. I have a rule like this, which works:
{code}
<relocation>
<pattern>io.netty</pattern>
<shadedPattern>com.couchbase.client.deps.io.netty</shadedPattern>
</relocation>
{code}
Now I also have code which lives under com.couchbase.client.deps in a different
source base that I don't want to relocate, because what ends up happening is I
get:
{code}
com.couchbase.client.deps.com.couchbase.client.deps.io.netty
{code}
So I was thinking I use an exclude tag to get rid of that case:
{code}
<relocation>
<pattern>io.netty</pattern>
<shadedPattern>com.couchbase.client.deps.io.netty</shadedPattern>
<excludes>
<exclude>com.couchbase.client.deps.io.netty.handler.codec.memcache</exclude>
</excludes>
</relocation>
{code}
But it seems that this is plainly ignored (it has no effect). So I did it the
hacky way which works, but I wondered if there is a propery way to do it
through excludes (or there is a bug?):
{code}
<relocation>
<pattern>io.netty</pattern>
<shadedPattern>com.couchbase.client.deps.io.netty</shadedPattern>
</relocation>
<relocation>
<pattern>com.couchbase.client.deps.com.couchbase.client</pattern>
<shadedPattern>com.couchbase.client</shadedPattern>
</relocation>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
