Nice - thanks for the quick reply. Can I have that hour of my life back now :-)
We are using 2.0.9 and it's not a trivial thing to get people and our environments updated. Is this truly fixed in 2.0.<something beyond what I'm using>? Or 2.2.0? -----Original Message----- From: news [mailto:n...@ger.gmane.org] On Behalf Of Jörg Schaible Sent: Wednesday, May 06, 2009 7:30 PM To: users@maven.apache.org Subject: Re: <dependencyManagement> EJ Ciramella wrote: > I have a quick question about dependencyManagement - if moduleA has a > dependencyManagement tag that pulls in a pom that has a bunch of > dependencies. > > ModuleB depends on moduleA. During a build of ModuleB, I can see it > trying to get at the pom specified in the dependencyManagement section > of moduleA, but it can't seem to find it in our local repository. > Yet, building moduleA, there are no problems. > > Am I missing some thing with regard to how these import scoped > dependencies work? This is MNG-3553 ... see also current discussion on dev. I've been hit by Arnaud's case also. - Jörg --------------------------------------------------------------------- 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
