maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <Joerg.Schai...@Elsag-Solutions.com>
Subject RE: Conflicting Dependency Version Dilemna
Date Thu, 10 Aug 2006 13:42:40 GMT
Mike Perham wrote on Thursday, August 10, 2006 3:28 PM:

> I like it and I think that's a reasonable request.   Throw it in JIRA
> and maybe Santa will deliver it in 2.1. :-)

This *is* what MNG-1577 is about and it has been postponed since 2.0.1.
:-/

> 
> mike
> 
> craigmcc@gmail.com wrote on 08/09/2006 11:37:39 PM:
> 
>> It could define the version conflict resolution rules such that
>> <dependencyManagement> version declarations in *my* POMs
> (defined as the
> one
>> for this project or the explictly declared parent tree) always win
>> over version declarations that come from explicit or transitive
>> dependencies. That way, I can declare in a single parent POM all my
>> version dependency information for *all* my leaf node projects
>> (webapps in my case, but the same principle applies to any
>> environment where you are creating lots of individual artifacts that
>> share a common set of 
> dependencies) without
> having
>> to tediously edit all of the leaf POMs individually.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message