The import solution that Stephen suggests is the way to go. Kind of a pre-mixin support... I use that a lot for defining different sets of depMgmt. Very useful when you work with app servers of different versions to make it possible to work and test against the exact same version of dependencies that you will be using in runtime.
/Anders On Thu, Jun 24, 2010 at 10:26, Dunstan, Tom (SACE Board) < [email protected]> wrote: > > The best solution is to have either: > > > > 1. A project for spring 3 and a project for spring 2.5 that > > defines the dependencyManagement for each of the spring > > versions and then use dependency scope import to pull in the > > spring 3 or the spring 2.5 dependency version info (assumes > > that the same GAV coords exist in both versions of spring and > > only the versions/exclusions change, and or the transitive > > deps are pulling in the diffs) > > OK, I wasn't aware of scope import, I'll have a look. Thanks > > > 2. A project for spring 3 and a project for spring 2.5 that > > pull in all the deps for these and then just depend on either > > the spring 3 or the spring 2.5 version. > > This is pretty horrible. I just want a nice way to share > dependencyManagement information between projects so that it's defined > somewhere central. This proposal actually changes the pulled in > dependencies. > > Thanks for the suggestions > > Tom > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
