[
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313076#comment-313076
]
Herve Boutemy edited comment on MNG-3092 at 11/8/12 12:18 AM:
--------------------------------------------------------------
yes, Maven 3.1 can be a chance to do something
to me, the question is not "is a snapshot in a range?", because the reply is
obvious: yes, a snapshot is in the range since a range is a mathematical notion
with two bounds and an order (a comparison algorithm)
but the questionis more: "how does Maven choose the best match when multiple
artifacts are available matching restrictions?" (I say "restriction" to avoid
"range" and since ranges are only one form of restriction)
then we need a use case with a reproducible simple test to work on it (and I
need to look for where is the code that makes this choice)
is somebody interested in working in such a direction?
was (Author: hboutemy):
yes, Maven 3.1 can be a chance to do something
to me, the question is not "is a snapshot in a range", because the reply is
obvious: yes, a snapshot is in the range since a range is a mathematical notion
with two bounds and a comparison algorihtm
but the questionis more: "how does Maven choose the best match when multiple
artifacts are available matching restrictions" (I say "restriction" to avoid
"range" and since ranges are only one form of restriction)
then we need a use case with a reproducible simple test to work on it (and I
need to look for where is the code that makes this choice)
is somebody interested in working in such a direction?
> 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
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
