That looks good. Just to be clear, in that link it seemed to be a discussion of what to possibly add to maven...are you saying that is in maven now? Btw I use 2.1.0.
Also what do you think about http://code.google.com/p/assimilate/ mentioned in the bottom of this link? -Dave On Sat, Nov 7, 2009 at 9:10 AM, Anders Hammar <[email protected]> wrote: > Yes, you could use the "import" scope at the top level to import dependency > management defined in another pom (which could be the ones in D). > http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies > > /Anders > > On Sat, Nov 7, 2009 at 15:42, David Hoffer <[email protected]> wrote: > > > We have a large maven project where each component (or group of > artifacts) > > each uses dependencyManagement to control what versions are used and to > > specify exclusions, etc. At an individual component level this works > well. > > > > You can think of our project as being lots of new maven/components (A, B, > > C) > > that act as a facade around a legacy component D...so D is at the bottom > of > > the dependency graph. > > > > However we really need D's dependency management to be at the top level > > too. That is, lots of changes happen at the legacy component D and we > > don't > > want to have to manually track dependency changes there and copy to the > top > > level. > > > > Is there a way in maven to say, at the top-level, use D's dependencies > for > > me too? If not, how hard would it be to write a plugin that does this? > > >
