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

Tuomas Kiviaho edited comment on MNG-3092 at 3/23/13 4:36 AM:
--------------------------------------------------------------

@Scott Sosna - I'm using snapshot inclusion blocking approach which is already 
quite well covered by 
[Sergei|https://jira.codehaus.org/browse/MNG-3092?focusedCommentId=313516&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-313516].
 For other purposes the less intruding pluggable [Dependency 
Selector|http://wiki.eclipse.org/Aether/Transitive_Dependency_Resolution] 
approach as Jason suggested might be achievable even today by using javaagent 
and aspects. This would not require patching/forking nor tampering with current 
version range semantics.

@Sergei Ivanov/Kunalkumar Somani - For my purposes MNG-3328 would provide a way 
to combine the two separate settings.xml back to one using a system property or 
an environment variable (such as IS_M2RELEASEBUILD) so that proposed new CMD 
line options could be omitted.

PS. I don't mean any disrespect to anyone who has put effort - both in time 
and/or  patience - on to solving this matter. Comic served just as a reminder 
that every change breaks someones workflow.
                
      was (Author: tuomas_kiviaho):
    @Scott Sosna - I'm using snapshot inclusion blocking approach which is 
already quite well covered by Sergey. For other purposes the less intruding 
pluggable [Dependency 
Selector|http://wiki.eclipse.org/Aether/Transitive_Dependency_Resolution] 
approach as Jason suggested might be achievable even today by using javaagent 
and aspects. This would not require patching/forking nor tampering with current 
version range semantics.

@Sergei Ivanov/Kunalkumar Somani - For my purposes MNG-3328 would provide a way 
to combine the two separate settings.xml back to one using a system property or 
an environment variable (such as IS_M2RELEASEBUILD) so that proposed new CMD 
line options could be omitted.

PS. I don't mean any disrespect to anyone who has put effort - both in time 
and/or  patience - on to solving this matter. Comic served just as a reminder 
that every change breaks someones workflow.
                  
> 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
>
>
> 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