[
http://jira.codehaus.org/browse/MVERSIONS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189849#action_189849
]
Stephen Connolly commented on MVERSIONS-71:
-------------------------------------------
give me an integration test that shows what you want to happen and I'll
consider it.
AFAIK an appropriate cd to the pom you want to change and use of -N should do
exactly what you want to do....
namely change the version of the pom.xml in the current directory, and change
the references throughout the reactor...
if that is not working. give me an integration test case and I'll accept it as
a bug
> versions:set changes both parent and module version
> ---------------------------------------------------
>
> Key: MVERSIONS-71
> URL: http://jira.codehaus.org/browse/MVERSIONS-71
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Eric Lewis
>
> When using verions:set, my understanding is that setting a version on a
> project sets the version in that project and sets the same as parent version
> in each module.
> However, it also sets the specified version into the module version.
> Imagine the following constellation:
> project A: version 1.2.0-SNAPSHOT
> module A1: version 2.0.7-SNAPSHOT, parent is A with 1.2.0-SNAPSHOT
> Now, using versions:set -DnewVersion=1.2.0 gives me the following result:
> project A: version 1.2.0
> module A1: version 1.2.0, parent is A with 1.2.0
> The version of the module has been altered, but it shouldn't.
> The versions plugin should have an option "ignoreModuleVersion" to prevent
> this.
--
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
