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

Joniec Jacek commented on MNG-3092:
-----------------------------------

@Sergei, you are making so complicate here.... when you are working with big 
company it's very difficult to separate out repo team by team.... if Same team 
is working on different project and want SNAPSHOT version of team C thn.... and 
more over in same project it self if they want SNAPSHOT version of C and 
release version of A then this is valid use case.... We can not separate out 
repo team base we have common repo in entire organization one for SNAPSHOT and 
one for RELEASE and many company they have only one repo which contain release 
and SNAPSHOT... 
We want to solve this problem for everyone with minimal change.

If you are saying "Yes obviously" to IDE vendors to change their implementation 
thn please ask them first, are they ready to change? 

If we have problem in Maven feature then first we need to solve the problem in 
Maven without depending on other tools to support us...

Sorry, but I'm not agree with you.
                
> 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