Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
3.0-beta-1
-
None
-
linux x86_64, sun java 1.6.0_14
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
Attachments
Attachments
Issue Links
- is related to
-
MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
- Reopened
-
MENFORCER-94 Review evaluation of version ranges with regard to inclusion of snapshots
- Closed