You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2012/06/10 23:20:21 UTC
[jira] (MSHARED-167) dependency:tree omits batik-js
[ https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MSHARED-167.
---------------------------------
Resolution: Fixed
Fix Version/s: maven-dependency-tree-2.0
Assignee: Herve Boutemy
new DependencyGraphBuilder component created in [r1348663|http://svn.apache.org/viewvc?rev=1348663&view=rev]
this component has a Maven 2 implementation using "usual" DependencyTreeBuilder and a Maven 3 implementation using Maven 3 with Aether
Default implementation detects current Maven version and automatically switches between the 2
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Assignee: Herve Boutemy
> Fix For: maven-dependency-tree-2.0
>
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira