[
https://issues.apache.org/jira/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487418#comment-16487418
]
Tim Shaw commented on MNG-3092:
-------------------------------
We were about to use ranges in a CI/SemanticVersioning environment.
Without this 'fix' we have serious issues.
Please just implement it (as per the non-implemented 2.0 spec???)
> Resolution of version ranges with non-snapshot bounds can resolve to a
> snapshot version
> ---------------------------------------------------------------------------------------
>
> Key: MNG-3092
> URL: https://issues.apache.org/jira/browse/MNG-3092
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Reporter: Mark Hobson
> Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: MNG-3092.patch, MNG-3092.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
