[
http://jira.jboss.com/jira/browse/JBBUILD-417?page=all ]
Paul Gier closed JBBUILD-417.
-----------------------------
Resolution: Done
A patch was added to the maven issue. This problem mainly occurs when a dependency has
been renamed, and the older version (before the rename) comes before the direct dependency
on the newer version with the new name. The workaround for this until it gets fixed in
maven core is to exclude any transitive dependency that is causing a problem.
Change maven classpath ordering for dependencies
------------------------------------------------
Key: JBBUILD-417
URL:
http://jira.jboss.com/jira/browse/JBBUILD-417
Project: JBoss Build System
Issue Type: Feature Request
Components: Maven
Reporter: Paul Gier
Assigned To: Paul Gier
Fix For: Maven Build - Maint 2007
Original Estimate: 2 days
Time Spent: 1 day, 4 hours
Remaining Estimate: 4 hours
Currently maven puts transitive dependencies first in the compile and test classpaths.
It would be better to have direct dependencies listed first.
See this maven issue:
http://jira.codehaus.org/browse/MNG-3197
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira