[ http://jira.codehaus.org/browse/MNG-2059?page=comments#action_58272 ] 

Emmanuel Venisse commented on MNG-2059:
---------------------------------------

Have you try this:

in parent pom:
<dependencyManagement>
  <dependency>
    <groupId>your_groupId</groupId>
    <artifactId>your_artifactId</artifactId>
    <version>your_version</version>
    <type>pom</type>                 <!-- This dependency is a pom that 
contains a list of dependencies required by child project -->
  </dependency>
</dependencyManagement>

in child pom:
<dependency>
    <groupId>your_groupId</groupId>
    <artifactId>your_artifactId</artifactId>
</dependency>


> Add ability to depend on a group of dependencies with a single dependency 
> element.
> ----------------------------------------------------------------------------------
>
>          Key: MNG-2059
>          URL: http://jira.codehaus.org/browse/MNG-2059
>      Project: Maven 2
>         Type: New Feature

>  Environment: n/a
>     Reporter: Mike Whittemore
>     Priority: Minor

>
>
> It would be convenient and reduce maintenance if Maven2 has the ability to 
> create a group of dependencies and then reference them via a single 
> dependency entry. Something like this:
> In master pom:
> <dependencyGroups>
> &nbsp;&nbsp;<dependencyGroup>
> &nbsp;&nbsp;&nbsp;&nbsp;<name>logging</name>
> &nbsp;&nbsp;&nbsp;&nbsp;<dependencies>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<dependency>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<groupId>apache</groupId>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<artifactId>commons-logging</artifactId>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</dependency>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<dependency>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<groupId>apache</groupId>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<artifactId>log4j</artifactId>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</dependency>
> &nbsp;&nbsp;&nbsp;&nbsp;<dependencies>
> &nbsp;&nbsp;</dependencyGroup>
> </dependencyGroups>
> In child pom:
> <dependencies>
> &nbsp;&nbsp;<dependency>
> &nbsp;&nbsp;&nbsp;&nbsp;<group>logging</group>
> &nbsp;&nbsp;</dependency>
> </dependencies>
> In my particular case, we have a large software project with a large 
> hierarchy of sub-projects that is continually growing. Many of the projects 
> share the same dependencies, but do not necessarily have a parent-child 
> relationship. If I have several projects that need, for example, the same 12 
> ORB implementation dependencies, it would be nice to declare that group of 12 
> dependencies as a "group" and then reference it from each project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to