v-m-p:use-latest-releases does not update pom.xml to the latest mercury version
-------------------------------------------------------------------------------
Key: MVERSIONS-119
URL: http://jira.codehaus.org/browse/MVERSIONS-119
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Mac/Unix
Reporter: Jane Young
Priority: Critical
I'm using Maven 2.2.1 and versions-maven-plugin:1.2 with mercury versioning
rule.
The artifact versions in the maven repo are: 3.0.1, 3.0.1-1, 3.0.1-1.1
In maven versioning: 3.0.1<3.0.1-1 and 3.0.1-1.1<3.0.1 and 3.0.1-1.1<3.0.1-1
In mercury versioning: 3.0.1<3.0.1-1 and 3.0.1-1.1 > 3.0.1 and 3.0.1-1.1 >
3.0.1-1
I'd like to use mercury versioning rule, so I created a rule-set xml file:
<ruleset comparisonMethod="maven">
<rules>
<rule groupId="my.gropuId" artifactId="my.artifact"
comparisonMethod="mercury"/>
</rules>
</ruleset>
In my pom.xml file, the dependency is defined as:
<dependency>
<groupId>my.groupId</groupId>
<artifactId>my.artifact</artifactId>
<version>3.0.1</version>
</dependency>
I use v-m-p:use-latest-releases goal with -DrulesUri=http://host/rule-set.xml
to update the pom with the latest release. I expect the pom is updated with
3.0.1-1.1 instead it's updated with the version 3.0.1-1.
--
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
