That’s jar hell man. It’s a problem that exists whether or not maven is involved.
I forget the exact formula maven uses if 2 versions of the same jar are found. It will pick one of the two. If you decide it picked the wrong one, you can override it using the dependencyManagement section of the top pom. > -----Original Message----- > From: Phillip Hellewell [mailto:ssh...@gmail.com] > Sent: Friday, November 05, 2010 5:11 PM > To: Maven Users List; joerg.schai...@gmx.de > Subject: Re: The joys of dependencies > > On Fri, Nov 5, 2010 at 3:00 PM, Phillip Hellewell <ssh...@gmail.com> > wrote: > > Thanks Jeorg. I will look into having a dependencyManagement section > > in parent pom as you and Jon suggested. That should at least help > > alleviate things a bit... > > Sorry to reply to myself, but I have a really big question about all > this. How do you handle dozens of artifacts, all of which may have > several versions going concurrently, like on different branches. Is > there a single parent pom that contains all dependency versions for > all artifacts on all branches? That seems like it could get very > complicated. Or would have a bunch of different parent poms > (actually, that seems even more complicated.) > > Phillip > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org
