[
http://jira.codehaus.org/browse/MVERSIONS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261682#action_261682
]
Eric Pabst commented on MVERSIONS-81:
-------------------------------------
The reason why using SCM to "revert" the change doesn't work well is that other
properties in the vicinity may have changed since, so the revert could result
in conflicts. The more sure way is to use this plugin and specify the older
version.
> Update of properties does not update version anymore to a previous release
> --------------------------------------------------------------------------
>
> Key: MVERSIONS-81
> URL: http://jira.codehaus.org/browse/MVERSIONS-81
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Max Schaefer
> Attachments: MVERSIONS-81.diff
>
>
> Example
> <version.xxx>1.0.24-rc3</version.xxx>
> ...
> <property>
> <name>version.adt-dml</name>
> <dependencies>
> <dependency>
> <groupId>yyy</groupId>
> <artifactId>xxx</artifactId>
> <version>[1.0,2.0)</version>
> </dependency>
> </dependencies>
> </property>
> The latest release of xxx in my repository is 1.0.24-rc3.
> The latest snapshot of xxx in my repository is 1.0.25-SNAPSHOT.
> When I invoke update-properties with allowSnapshots=true my property is set
> to 1.0.25-SNAPSHOT. But when I invoke update-properties with
> allowSnapshots=false my property is not set back to 1.0.24-rc3 anymore. That
> worked in the version before release 1.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
