maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sören Chittka (JIRA) <>
Subject [jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
Date Fri, 13 Apr 2012 10:38:03 GMT


Sören Chittka commented on MNG-3092:

I think most of this discussion does not only apply to SNAPSHOTs but to any kind of qualifier.
If I define a version range of [3.0, 4.0), because I expect breaking changes in 4.0, then
I don't want any artifact belonging to the 4-series (no '4.0-alpha-1' and no '4.0-SNAPSHOT').
Last time I checked with Maven 3.0.4, '4.0-alpha-1' was included.

In oppostion to SNAPSHOTs, other qualified version (like '3.5-beta-2') should be included
in the range.
> Version ranges with non-snapshot bounds can contain snapshot versions
> ---------------------------------------------------------------------
>                 Key: MNG-3092
>                 URL:
>             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
> 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:!default.jspa
For more information on JIRA, see:


View raw message