[
https://issues.apache.org/jira/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953780#comment-16953780
]
Olof Larsson edited comment on MSHARED-167 at 10/18/19 3:52 PM:
----------------------------------------------------------------
I just added this related ticket with a completion bounty:
https://issues.apache.org/jira/browse/MDEP-662
was (Author: olof larsson):
I just added this related ticket with a completion bounty:
https://issues.apache.org/jira/browse/MNG-6786
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://issues.apache.org/jira/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 N. Glick
> Assignee: Herve Boutemy
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.3.4#803005)
