incorrect order of dependencies on maven-reporting-impl and doxia-site-renderer
leads to wrong doxia-core
---------------------------------------------------------------------------------------------------------
Key: MPLUGIN-105
URL: http://jira.codehaus.org/browse/MPLUGIN-105
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 2.4
Reporter: John Casey
Priority: Blocker
Since the 2.0.9 code for Maven preserves the ordering of dependencies in a POM
for artifact resolution, the order of these dependencies now matters. In the
plugin plugin, it specifies two dependencies that drag in different versions of
doxia-core...the ordering of these two direct dependencies results in an
incompatible doxia-core version (from the maven-reporting-impl version 2.0.4)
being chosen over that from doxia-site-renderer.
We need to either (a) exclude doxia-core from the transitive dependencies
brought in by maven-reporting-impl, or (b) state a direct dependency on
doxia-core. Which is done depends on whether the plugin plugin in fact makes
direct use of classes from doxia-core...
maven-plugin-plugin 2.4 is unusable from the current maven-2.0.9 code as a
result of this problem, unless the user specifies a plugin-level dependency in
their own POM on doxia-core 1.0-alpha-10.
--
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
