display-dependency-updates always reports newer versions for dependencies when
using ranges
-------------------------------------------------------------------------------------------
Key: MVERSIONS-98
URL: http://jira.codehaus.org/browse/MVERSIONS-98
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Rehat 5.3 linux
Maven 2.2.x and 3.0
versions-maven-plugin 1.2-SNAPSHOT, built from subversion trunk
Reporter: Erik Schepers
The {{display-dependency-updates}} goal always reports new versions for
dependencies that were specified with a version-range (in either the
dependencies, or dependencyManagement section of the pom.)
For example, in my pom.xml I declare the following dependency with a range:
{code}
...
<dependencies>
<dependency>
<groupId>some.group</groupId>
<artifactId>test</artifactId>
<version>[1.0, 2.0)</version>
</dependency>
</dependencies>
...
{code}
Say that the latest release of {{some.group:test}} is 1.2.41
Unleashing the {{display-dependency-updates}} goal on this pom, produces the
following:
{noformat}
...
[INFO] The following dependencies in Dependencies have newer versions:
[INFO] some.group:test .................................. [1.0,2.0) -> 1.2.41
[INFO]
...
{noformat}
This is not what I expected, since the latest version (1.2.41) is within the
declared range of {{[1.0,2.0)}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
