Maven Shared Components

dependency:tree omits batik-js

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: maven-dependency-tree-1.2
  • Fix Version/s: maven-dependency-tree-2.0
  • Component/s: maven-dependency-tree
  • Labels:
    None
  • Environment:
    Maven 3.0, Ubuntu, JDK 6.
  • Testcase included:
    yes
  • Number of attachments :
    1

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.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MPIR-237 Unexpected download

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNBMODULE-102 Transitive dependencies incorrectly processed in Maven 3

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MDEP-339 tree mojo doesn't work consistently with maven3

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MENFORCER-140 DependencyConvergence: upgrade maven-dependency-tree dependency to 2.0 for better Maven 3 support

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Jesse Glick made changes -
Field Original Value New Value
Link This issue is depended upon by MNBMODULE-102 [ MNBMODULE-102 ]
Benjamin Bentmann made changes -
Complexity Intermediate
Project Maven 2 & 3 [ 10500 ] Maven Shared Components [ 11761 ]
Key MNG-4870 MSHARED-167
Affects Version/s maven-dependency-tree 1.2 [ 14530 ]
Affects Version/s 3.0 [ 13142 ]
Component/s maven-dependency-tree [ 13264 ]
Component/s Dependencies [ 12028 ]
Herve Boutemy made changes -
Link This issue is depended upon by MDEP-339 [ MDEP-339 ]
Herve Boutemy made changes -
Link This issue is depended upon by MPIR-237 [ MPIR-237 ]
Herve Boutemy made changes -
Status Open [ 1 ] Closed [ 6 ]
Assignee Herve Boutemy [ hboutemy ]
Fix Version/s maven-dependency-tree-2.0 [ 14540 ]
Resolution Fixed [ 1 ]
Herve Boutemy made changes -
Link This issue is depended upon by MENFORCER-140 [ MENFORCER-140 ]

People

  • Assignee:
    Herve Boutemy
    Reporter:
    Jesse Glick
Vote (1)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: