You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kristian Nordal (JIRA)" <ji...@codehaus.org> on 2005/08/06 22:45:57 UTC
[jira] Created: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Declared dependency is not included when there exist an exclusion of the artifact in another dependency
-------------------------------------------------------------------------------------------------------
Key: MNG-705
URL: http://jira.codehaus.org/browse/MNG-705
Project: Maven 2
Type: Bug
Versions: 2.0-beta-1
Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
Reporter: Kristian Nordal
Priority: Minor
I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
<project>
...
<dependencies>
...
<!-- Hibernate -->
<dependency>
<groupId>hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.0.5</version>
<exclusions>
...
<exclusion>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
</exclusion>
...
</exclusions>
...
<dependency>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>3.1</version>
</dependency>
</dependencies>
...
</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
[jira] Updated: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=all ]
Brett Porter updated MNG-705:
-----------------------------
Fix Version: 2.0-beta-2
this a rather pointless thing to do, but a bug nonetheless :)
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Priority: Minor
> Fix For: 2.0-beta-2
>
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Updated: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=all ]
Brett Porter updated MNG-705:
-----------------------------
Component: maven-artifact
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Closed: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=all ]
Brett Porter closed MNG-705:
----------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-3)
2.0-beta-2
works due to other changes
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_46920 ]
Trygve Laugstol commented on MNG-705:
-------------------------------------
Brett's point was that it's pointless in itself to exclude something and then include it again, the single include would be sufficient as it would override the transitive dependency.
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Kaare Nilsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_46926 ]
Kaare Nilsen commented on MNG-705:
----------------------------------
ahh.. i see..
then it was all StupidUserException in my case ;)
sorry for that
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Updated: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=all ]
Brett Porter updated MNG-705:
-----------------------------
Assign To: Brett Porter
Remaining Estimate: 1 hour
Original Estimate: 3600
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Kaare Nilsen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_46908 ]
Kaare Nilsen commented on MNG-705:
----------------------------------
Well.. it is not always pointless.
Because of this bug in combination with errors in activemq poms. i could not use dependencyManagement to remove all the errors in the activemq pom, and resolve it in my own.
So when one comes across an invalid pom it could be very usefull to exclude it in the pom with error, and add the right one in your own pom
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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
[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Posted by "Kristian Nordal (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_44064 ]
Kristian Nordal commented on MNG-705:
-------------------------------------
Yes, I just stumbled upon it while playing around =)
> Declared dependency is not included when there exist an exclusion of the artifact in another dependency
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-705
> URL: http://jira.codehaus.org/browse/MNG-705
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347
> Reporter: Kristian Nordal
> Priority: Minor
> Fix For: 2.0-beta-2
>
>
> I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM:
> <project>
> ...
> <dependencies>
> ...
> <!-- Hibernate -->
> <dependency>
> <groupId>hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.0.5</version>
> <exclusions>
> ...
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> ...
> </exclusions>
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
> </dependency>
> </dependencies>
> ...
> </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