[
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322930#comment-322930
]
Sergei Ivanov commented on MNG-3092:
------------------------------------
@Joniec
To your [first
comment|https://jira.codehaus.org/browse/MNG-3092?focusedCommentId=322928&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-322928].
I know it may be difficult to explain, that is why I am asking for detailed
examples or use cases, so that we all can be sure we understand the problem in
the same way.
If team B *never* wants to pick up snapshots of team A, then this problem can
be solved pretty easily without changing Maven a bit. All they need to do is to
segregate their repositories (which is generally not a bad idea anyway):
1. Team A sets up separate release and snapshot repositories for their
artifacts.
2. Team B sets up a repository group for themselves that only includes the
release repo of team A.
This way, team B will only ever see the released versions of artifacts from
team A. Done.
As a matter of fact, both teams can even share the same release repository, it
is only the snapshot repositories that need to be segregated.
To your [second
comment|https://jira.codehaus.org/browse/MNG-3092?focusedCommentId=322929&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-322929].
Yes, obviously if we are going to introduce changes into Maven, IDE vendors
will have to support the new functionality eventually. Our implementation
choice does not really matter here. By default, however, everything should
continue to work the way it is now.
> 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
