You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bruce Brouwer (JIRA)" <ji...@codehaus.org> on 2006/03/08 21:17:23 UTC
[jira] Created: (MNG-2138) Exclusions in dependencies should not
exclude a direct dependency
Exclusions in dependencies should not exclude a direct dependency
-----------------------------------------------------------------
Key: MNG-2138
URL: http://jira.codehaus.org/browse/MNG-2138
Project: Maven 2
Type: Bug
Components: Ant tasks
Versions: 2.0, 2.0.1, 2.0.2
Environment: Any (tested on windows)
Reporter: Bruce Brouwer
Priority: Minor
Here's the situation: My pom declares a dependency on artifact B, but excludes the transitive dependency on C. This same pom also directly depends on C. When getting the dependencies, C does not show up in the list, even though it is a direct dependency. Here is the relevant section of the pom:
<project ...>
<dependencies>
<dependency>
<groupId>groupB</groupId>
<artifactId>artifactB</artifactId>
<exclusions>
<exclusion>
<groupId>groupC</groupId>
<artifactId>artifactC</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>groupC</groupId>
<artifactId>artifactC</artifactId>
</dependency>
</dependencies>
</project>
Then using that ant task:
<artifact:dependencies
pomrefid="maven.project"
pathId="compile.classpath"
verbose="true"
useScope="compile" />
--
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
[jira] Moved: (MANTTASKS-134) Exclusions in dependencies should not
exclude a direct dependency
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-2138 to MANTTASKS-134:
--------------------------------------------------
Affects Version/s: (was: 2.0.2)
(was: 2.0.1)
(was: 2.0)
2.0
2.0.1
2.0.2
Component/s: (was: Ant tasks)
dependencies task
Key: MANTTASKS-134 (was: MNG-2138)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Exclusions in dependencies should not exclude a direct dependency
> -----------------------------------------------------------------
>
> Key: MANTTASKS-134
> URL: http://jira.codehaus.org/browse/MANTTASKS-134
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.0.2, 2.0.1, 2.0
> Environment: Any (tested on windows)
> Reporter: Bruce Brouwer
> Assignee: Carlos Sanchez
> Priority: Minor
>
> Here's the situation: My pom declares a dependency on artifact B, but excludes the transitive dependency on C. This same pom also directly depends on C. When getting the dependencies, C does not show up in the list, even though it is a direct dependency. Here is the relevant section of the pom:
> <project ...>
> <dependencies>
> <dependency>
> <groupId>groupB</groupId>
> <artifactId>artifactB</artifactId>
> <exclusions>
> <exclusion>
> <groupId>groupC</groupId>
> <artifactId>artifactC</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>groupC</groupId>
> <artifactId>artifactC</artifactId>
> </dependency>
> </dependencies>
> </project>
> Then using that ant task:
> <artifact:dependencies
> pomrefid="maven.project"
> pathId="compile.classpath"
> verbose="true"
> useScope="compile" />
--
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
[jira] Closed: (MNG-2138) Exclusions in dependencies should not
exclude a direct dependency
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2138?page=all ]
Carlos Sanchez closed MNG-2138:
-------------------------------
Assign To: Carlos Sanchez
Resolution: Won't Fix
You don't exclude a dependnecy if after you are including it again
> Exclusions in dependencies should not exclude a direct dependency
> -----------------------------------------------------------------
>
> Key: MNG-2138
> URL: http://jira.codehaus.org/browse/MNG-2138
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0, 2.0.1, 2.0.2
> Environment: Any (tested on windows)
> Reporter: Bruce Brouwer
> Assignee: Carlos Sanchez
> Priority: Minor
>
>
> Here's the situation: My pom declares a dependency on artifact B, but excludes the transitive dependency on C. This same pom also directly depends on C. When getting the dependencies, C does not show up in the list, even though it is a direct dependency. Here is the relevant section of the pom:
> <project ...>
> <dependencies>
> <dependency>
> <groupId>groupB</groupId>
> <artifactId>artifactB</artifactId>
> <exclusions>
> <exclusion>
> <groupId>groupC</groupId>
> <artifactId>artifactC</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>groupC</groupId>
> <artifactId>artifactC</artifactId>
> </dependency>
> </dependencies>
> </project>
> Then using that ant task:
> <artifact:dependencies
> pomrefid="maven.project"
> pathId="compile.classpath"
> verbose="true"
> useScope="compile" />
--
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