|
||||||||
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 |
- [mojo-dev] [jira] (MVERSIONS-248) update-properties i... Ben Tatham (JIRA)
- [mojo-dev] [jira] (MVERSIONS-248) update-propert... Sergei Ivanov (JIRA)
- [mojo-dev] [jira] (MVERSIONS-248) update-propert... Ben Tatham (JIRA)
- [mojo-dev] [jira] (MVERSIONS-248) update-propert... Ben Tatham (JIRA)
- [mojo-dev] [jira] (MVERSIONS-248) update-propert... Ben Tatham (JIRA)
We had the same problem with versions-maven-plugin and version properties in reactor projects, but we solved it in a different way. For each reactor...
I think the end result is more "Maven way", where you have dependency versions centrally managed by top-level POM for all modules in the reactor. Also, versions-maven-plugin now works like a charm on the top-level POM, checking/updating all versions at once.