You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/02/15 10:10:20 UTC

[jira] Closed: (MNG-2059) Add ability to depend on a group of dependencies with a single dependency element.

     [ http://jira.codehaus.org/browse/MNG-2059?page=all ]
     
Brett Porter closed MNG-2059:
-----------------------------

     Assign To: Brett Porter
    Resolution: Won't Fix

Emmanuel's inclusion of the tag in <dependencyManagement> makes sure the dependencies aren't inherited if you don't want them. He's specified exactly what you asked for in a way that works today :)

> 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
>     Assignee: Brett Porter
>     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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org