[ 
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288221#comment-288221
 ] 

Lars Weber commented on MNG-3092:
---------------------------------

I can confirm this bug.
I don't see that the discussion is necessary, because the behavior is explained 
in the specification:

{quote}
*Incorporating SNAPSHOT versions into the specification*
{color:red}*Resolution of dependency ranges should not resolve to a snapshot 
(development version) unless it is included as an explicit boundary.*{color} 
There is no need to compile against development code unless you are explicitly 
using a new feature, under which the snapshot will become the lower bound of 
your version specification. As releases are considered newer than the snapshot 
they belong to, they will be chosen over an old snapshot if found.

It is possible that applications such as Continuum may have a mode that enables 
always resolving to the snapshot version, but this is external to the POM 
itself.
{quote}
Source:[http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges]

So my vote goes to the implementation according to the specification.
                
> Version ranges with non-snapshot bounds can contain snapshot versions
> ---------------------------------------------------------------------
>
>                 Key: MNG-3092
>                 URL: https://jira.codehaus.org/browse/MNG-3092
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Mark Hobson
>         Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to