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...

  1. we aggregated all dependencies from all modules into the dependencyManagement section of the top-level reactor POM.
  2. we removed versions from dependency declarations in the modules, so that they could inherit versions from the parent's dependencyManagement.

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.

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

Reply via email to