[MPLUGIN-105] incorrect order of dependencies on maven-reporting-impl and doxia-site-renderer leads to wrong doxia-core

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.4.1
• Component/s: Plugin Plugin
• Assignee: Brian E Fox
• Reporter: John Dennis Casey
• Created: 21/Mar/08 11:24
• Updated: 10/Mar/16 13:51
• Resolved: 21/Mar/08 12:49

Description

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.

Issue Links

• relates to: MNG-3473 site generation with 2.0.9 and plugin:report (2.4 ONLY) is broken