You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Bittner (JIRA)" <ji...@codehaus.org> on 2011/11/04 15:50:51 UTC
[jira] Created: (MNG-5193) Maven-Ranges
Maven-Ranges
------------
Key: MNG-5193
URL: https://jira.codehaus.org/browse/MNG-5193
Project: Maven 2 & 3
Issue Type: Improvement
Components: Dependencies
Affects Versions: 3.0.3, 2.2.1
Environment: All
Reporter: Christian Bittner
Referencing artifacts using ranges, for instance
<dependency>
<groupId>local</groupId>
<artifactId>Wumpelputz_Component</artifactId>
<version>[1.0.0,1.1.0)</version>
</dependency>
the most recent version artifact is referenced. This can be the last snapshot (for instance "1.0.9-SNAPSHOT") or the last release (for instance "1.0.8" if the "1.0.9-SNAPSHOT" build hasn't finished yet).
Please note: This can be a snapshot artifact even when in a context of a release build (maven-release-plugin), what I consider a major bug!!!
What we need (humbly ask for) is something like that:
<dependency>
<groupId>local</groupId>
<artifactId>Wumpelputz_Component</artifactId>
<version>[1.0.0,1.1.0)</version>
<includeSnapshots>false</includeSnapshots>
</dependency>
Using "<includeSnapshots>" we want to control, whether the last snapshot or the most recent release is to be referenced. This should be set to "false" by default.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira