[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_55945 ]
Kohsuke Kawaguchi commented on MAVEN-1345:
--
dom4j 1.4 causes MPXDOC-188 (and MPXDOC-38.) (note that even though they are
marked as closed, the issue isn't fixed yet.)
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54704 ]
Brett Porter commented on MAVEN-1345:
-
We should just stay on 1.4, at least until Jaxen releases 1.1 and Jelly
upgrades.
Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54708 ]
Elliotte Rusty Harold commented on MAVEN-1345:
--
The AElfred parser is indeed the problem I was referring to. If you pull it out
of the JAR file, dom4j 1.4 should be
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53816 ]
Elliotte Rusty Harold commented on MAVEN-1345:
--
Please do not use dom4j 1.4 or earlier. It has some license issues that weren't
corrected until about 1.6. I have to check
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53877 ]
Lukas Theussl commented on MAVEN-1345:
--
I suppose it is the use of the Aelfred2 parser that was removed in the 1.5.2
release (http://www.dom4j.org/changes-report.html#1_5_2).
But
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53878 ]
Brett Porter commented on MAVEN-1345:
-
If its the Aelfred2 parser, we don't use it. We can surgically remove it from
the JAR. The dom4j project should also ask us to retract or
