[mojo-dev] [jira] (MVERSIONS-199) Changing versions in a nested module structure

[Valentin Baranov (JIRA)]

Valentin Baranov reopened MVERSIONS-199 Changing versions in a nested module structure Thank you for the quick answer. I tried once again - and the versions of child poms didn't change. I used the following command: mvn vesrions:set -DoldVersion=<currentVersionValue> -DnewVersion=<versionNumberWeNeed> The version value changed only in parent pom. We also cannot use project.version or project.parent.version properties because they are forbidden in maven 3. Do you have any ideas about this? Change By: Valentin Baranov (29/Nov/12 3:14 AM) Status: Closed Reopened Resolution: Not A Bug

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. 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