Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
maven-dependency-tree-1.2
-
None
-
Maven 3.0, Ubuntu, JDK 6.
Description
(Not sure what the right place to file this is. maven-dependency-tree 1.2 gives MNG as the JIRA component by inheritance.)
mvn dependency:tree on the attached project lists batik-script by way of batik-bridge as expected, but then fails to show batik-js as a dependency of that. If you list batik-script as a direct dependency, batik-js is correctly shown.
Possibly related is that Maven 2.2.1 also fails to find batik-js in MavenProject.getRuntimeArtifacts, so clean package fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits batik-js, and there may be other user-visible effects of this bug.
Attachments
Attachments
Issue Links
- is depended upon by
-
MPIR-237 Unexpected download
- Closed
-
MDEP-339 tree mojo doesn't work consistently with maven3
- Closed
-
MENFORCER-140 DependencyConvergence: upgrade maven-dependency-tree dependency to 2.0 for better Maven 3 support
- Closed
- is related to
-
MDEP-662 Re-Add Dependency Tree Verbose
- Closed