You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/07/08 23:23:23 UTC
[jira] Updated: (MNG-3196) Allow exclusion of a certain transitive
dependency across all direct dependencies.
[ http://jira.codehaus.org/browse/MNG-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MNG-3196:
---------------------------
Description:
I would like to be able to put exludes at the top level of dependencies so that it can easily be excluded from all transitive dependencies, instead of just excluding it from a single dependency at a time. For example assume that project1 and project2 both have transitive dependencies on different versions of project-trans:
{code:xml}
<dependencies>
<exclusions>
<exclusion>
<groupId>com.stuff</groupId>
<artifactId>project-trans</artifactId>
</exclusion>
</exclusions>
<dependency>
<groupId>com.stuff</groupId>
<artifactId>project1</artifactId>
<version>1.0</version>
<dependency>
<dependency>
<groupId>com.stuff</groupId>
<artifactId>project2</artifactId>
<version>1.0</version>
<dependency>
</dependencies>
{code}
In this example, the "project-trans" dependency would be exluded from both project1 and project2. It can be difficult to find all the locations of a transitively included dependency for a large project that has a large number of frequently changing dependencies.
was:
I would like to be able to put exludes at the top level of dependencies so that it can easily be excluded from all transitive dependencies, instead of just excluding it from a single dependency at a time. For example assume that project1 and project2 both have transitive dependencies on different versions of project-trans:
<dependencies>
<exclusions>
<exclusion>
<groupId>com.stuff</groupId>
<artifactId>project-trans</artifactId>
</exclusion>
</exclusions>
<dependency>
<groupId>com.stuff</groupId>
<artifactId>project1</artifactId>
<version>1.0</version>
<dependency>
<dependency>
<groupId>com.stuff</groupId>
<artifactId>project2</artifactId>
<version>1.0</version>
<dependency>
</dependencies>
In this example, the "project-trans" dependency would be exluded from both project1 and project2. It can be difficult to find all the locations of a transitively included dependency for a large project that has a large number of frequently changing dependencies.
> Allow exclusion of a certain transitive dependency across all direct dependencies.
> ----------------------------------------------------------------------------------
>
> Key: MNG-3196
> URL: http://jira.codehaus.org/browse/MNG-3196
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.7
> Reporter: Paul Gier
> Fix For: 3.x
>
>
> I would like to be able to put exludes at the top level of dependencies so that it can easily be excluded from all transitive dependencies, instead of just excluding it from a single dependency at a time. For example assume that project1 and project2 both have transitive dependencies on different versions of project-trans:
> {code:xml}
> <dependencies>
> <exclusions>
> <exclusion>
> <groupId>com.stuff</groupId>
> <artifactId>project-trans</artifactId>
> </exclusion>
> </exclusions>
> <dependency>
> <groupId>com.stuff</groupId>
> <artifactId>project1</artifactId>
> <version>1.0</version>
> <dependency>
> <dependency>
> <groupId>com.stuff</groupId>
> <artifactId>project2</artifactId>
> <version>1.0</version>
> <dependency>
> </dependencies>
> {code}
> In this example, the "project-trans" dependency would be exluded from both project1 and project2. It can be difficult to find all the locations of a transitively included dependency for a large project that has a large number of frequently changing dependencies.
--
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