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 Mon, 04 Aug 2014 18:55:16 GMT

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

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

We use, and many others use Maven version ranges with pleasure. They work exactly as they
should, snapshots come into ranges just as they should. As long as you know how they work,
you can build easily and cleanly with them. There is no problem here. 

However, Mark and I are doing a spike on a version range resolver plugin that uses the LifecycleParticipant
model to change how artifacts are resolved (compile always lowest in a range, test and release
always highest). Perhaps you can fork it once its done (if we can get it to work).

> 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