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

Scott Sosna commented on MNG-3092:
----------------------------------

Have we narrowed it down to just these two approaches?  And does it solve all 
the issues in this thread?  I see some discussions about versions 4.0-alpha-1 
and should it behave like 4.0-SNAPSHOT, I'm concerned we've addressed the 
happy-path (not that there's anything happy here) and want to make sure 
everything is addressed (even the statement is "that's silly").

Also, what are the performance impacts on either of these approaches?  For my 
projects, Maven3 is substantially slower in resolving versions, making things 
like the Eclipse m2e plugin borderline useless.  Dependencies need to be 
resolved as quickly as in Maven2.

If these are the two approaches, who approaches the Maven committers or 
whomever to get signoff on an approach and get it commited to the branch?
                
> 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.1.1
>
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to