[
http://jira.codehaus.org/browse/MNG-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey reopened MNG-3503:
-----------------------------
Assignee: Benjamin Bentmann (was: John Casey)
When building a POM project with a site descriptor, this change causes a
linkage error on XmlSerializer (from Xpp3Dom). Looking around on the java
forums, I found this:
http://forum.java.sun.com/thread.jspa?messageID=3902289
which seems to hint that processing the Xpp3Dom class to change package names
for anything at all might cause this problem. I'm not entirely sure I
understand this problem, but I'm adding a new IT to the core-integration-tests
to check this scenario for future changes.
Unfortunately, this issue won't make it into 2.0.10 as a result. This problem
seems to indicate a level of risk for this change that I'm simply uncomfortable
with at this stage.
> Shade MX* classes from plexus-utils
> -----------------------------------
>
> Key: MNG-3503
> URL: http://jira.codehaus.org/browse/MNG-3503
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.0.8
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 2.0.11
>
> Attachments: shade-mx-classes.patch
>
>
> The Maven uber JAR currently ships with unshaded {{MXParser}} and
> {{MXSerializer}}, preventing plugins from using their recent implementations
> from plexus-utils. My initial question on the [dev
> list|http://www.nabble.com/Shade-MX*-classes-from-plexus-utils--tc16080800s177.html]
> showed now immediate objections and the core ITs also smile so here we go
> with the proposed patch.
--
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
