[
http://jira.codehaus.org/browse/MSHADE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162140#action_162140
]
Benjamin Bentmann commented on MSHADE-30:
-----------------------------------------
bq. could you do me a favor and provide an example of said "non-sense
<relocation>" stuffs?
Something like the following should do:
{code:xml}
<relocations>
<relocation>
<pattern>void</pattern>
<shadedPattern>void</shadedPattern>
</relocation>
</relocations>
{code}
i.e. a relocation that doesn't actually affect one's classes but exists merely
to trigger another code path in the plugin.
bq. Also for me, at least, changing pom.xml to say [...] <version>1.2</version>
fixed it
Which isn't suprising given that this issue is marked as "Fix Version: 1.2" ;-)
> duplicate entry error
> ---------------------
>
> Key: MSHADE-30
> URL: http://jira.codehaus.org/browse/MSHADE-30
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.0.1
> Reporter: Michael Mattox
> Assignee: Benjamin Bentmann
> Fix For: 1.2
>
> Attachments: mshade-30-patch.txt
>
>
> I receive this error:
> Embedded error: duplicate entry: org/apache/xmlbeans/FilterXmlObject.class
> It started with a javax.xml.namespace class. So I started putting excludes,
> and then I kept getting one new class after another. If I exclude everything
> then I doubt my application is going to work.
> I really don't understand this error. I have never seen this type of error
> with the fatjar eclipse plugin. I understand it's complaining about having
> the same class twice, but if it's not a problem for my eclipse project or the
> maven build, why is it a problem for shade?
> I feel the shade plugin should be able to handle this gracefully.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
