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

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

My questions are: will the Maven core team accept a patch that only addresses a 
portion of this discussion?  And if not addressed, how do we avoid extending 
discussions on this issue another 6 years?!?

I fully agree with wanting to take incremental steps, and hopefully this is 
acceptable.  I also know that the current implementation resolves dependencies 
magnitudes slower than what was in Maven2.  Locking down the behavior is fine, 
but it doesn't help me if the overall performance doesn't increase as well.  I 
have Eclipse users breathing down my back who want to flat-out ditch Maven 
because of the Eclipse plug-in problem (the plug-in insists on embedding Maven3 
with no way to override it for dependency resolution).

So dealing with just a subset may not be enough, for me, for others, for the 
core team.  And if it's not, the previous functionality of Maven2 (and very 
early Maven3) should be restored.
                
> 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