Create one shared parent pom with a <dependencyManagement> section that they all inherit.
Then in your project pom dependency sections, leave out the version. It will be inherited from the shared parent. Wayne On 2/22/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote: > Hello, > > We have lots of projects in our environment which most of them are small > stand alone projects with not much dependency to each other. Every project > has its own maven build system ( or going to have, we are in process of > migrating the build system). I am seeking a way to ensure that all of the > application are using one specific version of external artifact. For example > if three projects are depend on struts, I would love to have a > tool/mechanism to force all of them version 1.3.8; and in case we wanted to > upgrade our struts dependency, we can do it one place instead of changing > all the dependencies. > Any suggestion? Can Archiva give us this kind of control? > > regards, > Arash > > -- > You can not depend on your eyes when your imagination is out of focus. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
