Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Patch
Description
Contrary to the 2.0 design docs:
"Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary."
– from http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification
The following is equates to true:
VersionRange.createFromVersionSpec( "[1.0,1.1]" ).containsVersion( new DefaultArtifactVersion( "1.1-SNAPSHOT" ) )
The attached patch only allows snapshot versions to be contained in a range if they are equal to one of the boundaries. Note that this is a strict equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT.
Attachments
Attachments
Issue Links
- Dependent
-
MNG-6049 Add behavior to filter resolved version ranges of an artifact
- Reopened
- is depended upon by
-
MRELEASE-318 Release plugin throws NullPointerException when using version range for dependency
- Closed
-
MNG-2994 Snapshot repositories are not checked when using ranges
- Closed
- is duplicated by
-
MNG-3001 Maven2 does not resolve version ranges correctly [PATCH INCLUDED]
- Closed
-
MNG-3109 version ranges can include snapshots
- Closed
-
MNG-4089 Allow LATEST and RELEASE to peg major version similar to SNAPSHOT
- Closed
- is related to
-
JCR-4626 CI build fail because org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT can't be retrieved
- Closed
-
MNG-7960 Artifact collection filtering
- Closed
- relates to
-
MNG-4751 Snapshot version not resolved for version range
- Closed
-
MRELEASE-216 Release plugin should ignore SNAPSHOTS that are not specified in the POM
- Closed
-
MNG-4295 version ranges are not resolved from snapshot only repositories
- Closed
-
MNG-5353 Ignore pre-releases in exclusive upper bound [lw,up)
- Open
-
MENFORCER-94 Review evaluation of version ranges with regard to inclusion of snapshots
- Closed
- links to