Maven 2 & 3

Snapshot version not resolved for version range

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 3.0-beta-1
  • Fix Version/s: 3.0
  • Component/s: Dependencies
  • Labels:
    None
  • Environment:
    linux x86_64, sun java 1.6.0_14
  • Complexity:
    Intermediate
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

Even with a snapshot dependency in the pom, a release version is included in the classpath for compilation.

This happens when a mid-level dependency and the top-level project both depend on the same artifact. The mid-level dependency selects a range of valid versions which includes the snapshot version and the top-level project depends explicitly on the snapshot version.

This is a regression from 2.2.1

To reproduce:
1. Release/deploy/install v1.0 of tlib
2. deploy v1.1-SNAPSHOT of tlib
3. Release/deploy/install v1.0 of tlib2
4. Try to compile tapp

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3092 Version ranges with non-snapshot bounds can contain snapshot versions

  • Major - Major loss of function.
  • Reopened - This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

Task - A task that needs to be done. MENFORCER-94 Review evaluation of version ranges with regard to inclusion of snapshots

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

No work has yet been logged on this issue.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Brian Kramer
Vote (3)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: