Maven 2.x Dependency Plugin

tree mojo doesn't work consistently with maven3

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.5
  • Component/s: tree
  • Labels:
    None
  • Number of attachments :
    0

Description

see MSHARED-167: independently from dependency:tree, M2 has a wrong artifact list resolution (missing one transitive artifact) where M3 has a fixed one.

But dependency:tree with M3 shows the same (wrong, ie with one missing transitive dependency) resolution tree as M2: dependency:tree needs to be consistent with resolved artifact list

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MSHARED-167 dependency:tree omits batik-js

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

Bug - A problem which impairs or prevents the functions of the product. MDEP-356 maven dependency plugin should use maven 3 dependency resolver, aether

  • 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. MDEP-393 Result of tree and list differs

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

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. MDEP-374 dependency:tree -Dverbose isn't verbose anymore

  • 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.

Activity

No work has yet been logged on this issue.

People

  • Assignee:
    Herve Boutemy
    Reporter:
    Olivier Lamy
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: