maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Vowles (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
Date Sat, 02 Aug 2014 20:51:13 GMT

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

Richard Vowles commented on MNG-3092:
-------------------------------------

No, of course I am not being sarcastic. We use version ranges all the time everywhere, and
it works perfectly well. You always release from 1.1 and never, ever release a 1.0 version.
Then [1,2) works entirely as expected. I have used version ranges in my last two major jobs
and if you stick that that *simple* rule, there is absolutely zero problem. We use the bounds
plugin to auto pull-up lower bounds, we just released the Maven Tiles plugin and it uses and
supports version ranges (http://github.com/repaint-io/maven-tiles), the Groovydoc plugin uses
it, the Karma plugin uses it. Version ranges just simply work perfectly well, just start at
1.1.

> resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-3092
>                 URL: https://jira.codehaus.org/browse/MNG-3092
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Mark Hobson
>            Assignee: Jason van Zyl
>             Fix For: 3.2.x
>
>         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 was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message