Thanks to everyone who answered my questions! Import scope seems to be doing 
exactly what I want.

Cheers

Tom


Tom Dunstan
Senior Analyst/Programmer  

SACE Board of South Australia
P   +61 8 8372 7543 

> -----Original Message-----
> From: anders.g.ham...@gmail.com 
> [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar
> Sent: Thursday, 24 June 2010 6:09 PM
> To: Maven Users List
> Subject: Re: Activating profiles declared in parent pom
> 
> 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) < 
> t...@saceboard.sa.gov.au> 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: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to