On Fri, Dec 12, 2008 at 7:45 AM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Hmmmm.... you've just given me an idea for a mojo for the > versions-maven-plugin
As Stephen points out in the JIRA, the correct way is to add a dependencyManagement section. Dependencies need to be MANAGED. Someone needs to take this ownership, your tech lead/architect is a good choice. Otherwise you end up in chaos. The usual way to handle this is to have all your projects inherit from a common pom and define all versions in the dependencyManagement section. Then all your children artifacts NEVER define versions. They will always select the correct version from your parent or throw an error - which indicates you need to include that artifact in the parent dependencyManagement section. Yes its a pain and the versions-maven-plugin new feature would make this work easier, but it is something that you have to actively manage to avoid testing or conflict issues. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
