[
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322417#comment-322417
]
Scott Sosna commented on MNG-3092:
----------------------------------
Tuomas: If you have problems with this approach, what is an approach that works
and can address the issues mentioned in this thread? I don't know enough about
your workflow, but it would seem that different settings.xml wouldn't require
the tedious changes you mentioned in your last paragraph, wouldn't require
resetting after releasing.
After 5.75 years, this issue must be addressed. Kunalkumar proposes an
approach, instead of finding faults with every approach/suggestion, let's use
this as a line-in-the-sand and refine it further. We need a starting point,
this seems reasonable in its assumptions. Also realizing that no solution is
going to please everyone, what's proposed at least is sensible and is not
broken like the current Maven3 range functionality.
Or, let's admit defeat and restore what's in Maven2. Yes, it's broken, but no
more so than what's in Maven3 (and probably less so). At that point, instead
of rewriting range functionality, small incremental changes can be made,
evaluated, extended, etc. But what we have now is ridiculous.
...and this couldn't illustrate any better why outsiders get frustrated with
software developers. Even Debian's come out with 2 releases in the same
timeframe.
> 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
