Maven 2 & 3

POM dependency scope auto-downgrades from provided to test

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0.4
  • Fix Version/s: 3.0-beta-3
  • Component/s: Dependencies
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

My project has a dependency on:
XXX:YYY:jar:1.0-SNAPSHOT (selected for null)
with transitive dependency:
commons-logging:commons-logging:jar:1.1:test
and again triggering a transitive dependency on:
javax.servlet:servlet-api:jar:2.3:test (selected for test)

Later on the project also has a dependency:
AAA:BBB-container:pom:1.0-SNAPSHOT:provided (selected for provided)
I use this to represent the dependencies provided by the J2EE container in which the application will be deployed.
This triggers via:
tomcat:catalina:jar:5.5.15:provided (selected for provided)
the following funny thing:
javax.servlet:servlet-api:jar:2.4:provided (removed - nearer found: 2.3)

Leaving me without servlet-api for the compile scope.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNG-2101 transitive dependency: test stronger than provided

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

Bug - A problem which impairs or prevents the functions of the product. MNG-1895 Dependencies in two paths are not added to resolution when scope needs to be updated in the nearest due to any of nearest parents

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Frank Cornelis
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: