Maven 2 & 3

Dependencies in two paths are not added to resolution when scope needs to be updated in the nearest due to any of nearest parents

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.0.1, 2.0.2
  • Fix Version/s: 2.0.3
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Expert
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

scopes are not correctly calculated for this case

my pom: a compile, b test
a: c compile, d compile
b: d compile

then d ends in test scope because d is closer to my project through the path b-d

I think scope importance should also be taken into account

Issue Links

is depended upon by

Sub-task - The sub-task of the issue MNGBOOK-57 Release maven 2.0.3

  • 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. MNG-1568 test-jar dependency clobbers transitive dependency

  • 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. MNG-1571 Wrong calculation of transient dependecies if artifact is referenced from different scopes

  • 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. MNG-4724 Plugin runtime classpath during execution differs from runtime classpath during building when conflicts with test/provided scope dependencies are involved

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MNG-2686 POM dependency scope auto-downgrades from provided to test

  • Critical - Crashes, loss of data, severe memory leak.
  • 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. MNG-4675 Compile scoped dependencies replaced by test

  • 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. MNG-4789 [regression] Difference in compile scope dependency resolution

  • 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
Hide
Permalink
Carlos Sanchez added a comment -

This is the it test

Show
Carlos Sanchez added a comment - This is the it test
Hide
Permalink
John Casey added a comment -

bumping to next release, so we can assess any changes to existing behavior that this might imply.

Show
John Casey added a comment - bumping to next release, so we can assess any changes to existing behavior that this might imply.
Hide
Permalink
Carlos Sanchez added a comment -

This is ablocker issue if you need to depend in a test-jar type artifact and its normal jar, as it'll make all its deps end in scope test

Show
Carlos Sanchez added a comment - This is ablocker issue if you need to depend in a test-jar type artifact and its normal jar, as it'll make all its deps end in scope test

People

  • Assignee:
    Carlos Sanchez
    Reporter:
    Carlos Sanchez
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: