Classpath dependency resolution may result in duplicates or conflicts for transitive dependencies

[GoogleCodeExporter]

When <useProjectDependencies> is specified, the project dependencies for the 
specified scope(s) are programmatically resolved transitively, but on a 
one-by-one basis. That means that if two project dependencies have a common 
transitive dependency, it will be duplicated, even with conflicting versions.

The attached patch changes the resolution mechanism for dependencies to instead 
be resolved by the Plugin API (using the standard dependency resolution 
mechanism), which gives the expected behavior.

Original issue reported on code.google.com by bjorn.be...@callistaenterprise.se on 20 Nov 2013 at 3:28

[GoogleCodeExporter]

Original comment by bjorn.be...@callistaenterprise.se on 9 Dec 2013 at 1:32

Attachments:

• resolve-dependencies.patch

[GoogleCodeExporter]

Original comment by stewart@javahelp.co.uk on 9 Jun 2014 at 11:38

• Changed state: Accepted
• Added labels: Release-1.4.0

[GoogleCodeExporter]

Fix committed to /trunk at r403. SNAPSHOT deployed to repo.

Original comment by stewart@javahelp.co.uk on 4 Jul 2014 at 2:22

• Changed state: Fixed