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

Sergei Ivanov commented on MNG-3092:
------------------------------------

@Scott: You are probably out of luck, as last month Maven 2.x was unanimously 
voted to be EOL-ed. See the following thread:
http://mail-archives.apache.org/mod_mbox/maven-dev/201402.mbox/%3CCA%2BnPnMyTkdW5atYgDovh2BdHs6O%3DGiNbSzOo0ZMJds6ooWRPkQ%40mail.gmail.com%3E

I doubt that this issue is going to be resolved in any 3.x builds either, 
because 3.x seems to be moving into a maintenance mode now (this is my personal 
impression though). However, I do hope that Jason&Co. will consider this as a 
high priority for Maven4. I have an impression that Maven4 will bring model 
changes about, and that may help solving this problem in an elegant way. I 
would prefer to see a proper solution rather that an attempt to shoehorn some 
terrible kludge into the existing model. We managed to work around the issue so 
far by setting up our CI and dev environment in a specific way (see above). 
Provided that this issue is on the hit list for Maven4, our team can wait.

> 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
>            Assignee: Jason van Zyl
>             Fix For: 3.2.x
>
>         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
(v6.1.6#6162)

Reply via email to