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 2005/11/02 08:07:47 UTC
[jira] Closed: (MNG-1286) Check exclusions against relocated artifacts
[ http://jira.codehaus.org/browse/MNG-1286?page=all ]
Brett Porter closed MNG-1286:
-----------------------------
Assign To: Lester Ecarma (was: Edwin Punzalan)
Resolution: Fixed
> Check exclusions against relocated artifacts
> --------------------------------------------
>
> Key: MNG-1286
> URL: http://jira.codehaus.org/browse/MNG-1286
> Project: Maven 2
> Type: Improvement
> Versions: 2.0
> Reporter: Carlos Sanchez
> Assignee: Lester Ecarma
> Fix For: 2.0.1
> Attachments: MNG-1286-maven-artifact_b.patch, MNG-1286-maven-project_b.patch, MNG-1287-maven-project.patch
>
>
> When using an artifact that was relocated you need to exclude the one used directly, it doesn't work if you use the final relocated artifact. This is confusing when you get an artifact in your war but you need to exclude other.
> eg. if you don't use exclusions you get jdbc-stdext in the war. Using option b doesn't work, currently you need to use option a.
> <dependency>
> <artifactId>commons-dbcp</artifactId>
> <groupId>commons-dbcp</groupId>
> <version>1.2</version>
> <exclusions>
> <!-- option a -->
> <exclusion>
> <artifactId>jdbc</artifactId>
> <groupId>jdbc</groupId>
> </exclusion>
> <!-- option b -->
> <exclusion>
> <artifactId>jdbc-stdext</artifactId>
> <groupId>javax.sql</groupId>
> </exclusion>
> </exclusions>
> </dependency>
--
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