You can specify a pom dependency in any project just as you would any other dependency and the transitions take care of the rest...
using standard OO prinicples you can encapsulate a common set of deps in a another project and depend on it from many, there is no need for the dependency management section one might even argue that makes it way more complicated that is necessary On Mon, 28 Jan 2008 20:07:36 Rohnny Moland wrote: > Hei, > > I am trying to figure out the best way to group dependencies for > easier maintainance. I was reading this: > > <http://www.mail-archive.com/[EMAIL PROTECTED]/msg61076.html> > > Which is close to what I am looking for. Is this something that is > going to be implemented in a later maven version? > > I also know that today it is possible to do what is described here: > > <http://jira.codehaus.org/browse/MNG-2059> > > This is a nice solution if you have 1 dependency group, but not so > nice if you have 3, because one pom can only inherit from one another > pom. Lets say: > > parent pom > ^ > test-deps pom > ^ > gui-deps pom > ^ > product A > ^ > jar module 1 > jar module 2 > .. > > Any other ways to do this? Would be nice if maven had multiple inheritance. > > > Thanks, > Rohnny > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
