You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Erik Schepers (JIRA)" <ji...@codehaus.org> on 2011/01/13 09:03:58 UTC
[jira] Commented: (MNG-3092) Version ranges with non-snapshot
bounds can contain snapshot versions
[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251429#action_251429 ]
Erik Schepers commented on MNG-3092:
------------------------------------
I strongly agree with Syvalta.
We are currently using ranges in our projects, and are now only able to perform releases on maven-3.0-beta-1, as this issue was resolved in that version only. As I understand the enforcer-plugin does not solve this problem, it provides only an after-the-fact observation.
The specification has been clear, so why not fix this issue on the short term (3.0.2?)
I wouldn't mind to have to add the {{\[x,y){use-snapshots=false\}}} to explicitly exclude snapshots, while the default behaviour stays as it is now (include snapshots in the range). I also wouldn't mind a command-line option to disable snapshots in ranges explicitly.
But at least I need something to be able to perform a release in combination with version-ranges. With the current state of maven-3, that's not possible (or at least I don't know how).
> Version ranges with non-snapshot bounds can contain snapshot versions
> ---------------------------------------------------------------------
>
> Key: MNG-3092
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira