Dependency Versions - Makeover

Stefan Negrea snegrea at redhat.com
Fri Mar 15 17:47:03 UTC 2013



----- Original Message -----
> From: "Heiko W.Rupp" <hrupp at redhat.com>
> To: rhq-devel at lists.fedorahosted.org
> Sent: Friday, March 15, 2013 12:09:10 PM
> Subject: Re: Dependency Versions - Makeover
> 
> 
> Am 15.03.2013 um 17:39 schrieb John Mazzitelli:
> > I like the idea of having everything like this defined in one place
> > (the root pom). If its large, so be it. The alternative is going
> > through our large set of poms to adjust things that we need.
> 
> I also like the root pom idea.
> 
> But: doesn't that only solve a small part of the puzzle?
> 
> If we e.g. support commons-frobnitz:3.15.13
> and as7 wants commons-frobnitz:2.12.22
> and gwt has a dependency of commons-frobnitz:4.0.0-ALPHA
> 
> we still end up with 3 versions of the same library with potentially
> all the issues
> 
> But then I am probably missing something, as I am no maven expert at
> all

>From what I know this will not be the case. If a dependency version is explicitly declared in the dependencyManagement section then all the dependencies that require it are forced to use it. 


So in your example, to make sure we only one single version of commons-frobnitz we would need to add it to the dependencyManagement section with the desired version (let's say 3.15.13).


> 
> 
> 
> 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 


More information about the rhq-devel mailing list