maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arik Kfir (JIRA)" <>
Subject [jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
Date Mon, 22 Nov 2010 18:34:04 GMT


Arik Kfir commented on MNG-3092:

+1 for including SNAPSHOTs in the version ranges if the artifact is in the reactor. I also
liked the [x,y){use-snapshots=true} proposal.
I also agree that this is a process problem and should be enforced by the enforcer plugin,
rather than maven core itself. 

Btw, besides CI builds, another use-case in favor of including SNAPSHOTs in ranges is IDE
integration; we have a project consisting of multiple inter-dependant modules and having them
resolve to each-other using ranges is very convenient, rather than updating the POMs everytime
one of them is released.

> 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 contact one of the administrators:
For more information on JIRA, see:


View raw message