[ http://jira.codehaus.org/browse/MNG-1797?page=comments#action_57831 ]
Cameron Braid commented on MNG-1797:
------------------------------------
Say for example you have this :
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-hibernate3</artifactId>
<version>2.0-m1</version>
<exclusions>
<exclusion>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.1</version>
</dependency>
hibernate 3.1 will be excluced.
Of course, you could always explicitly exclude the specific version
> Dependency excludes apply to every subsequent dependency, not just the one it
> is declared under.
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-1797
> URL: http://jira.codehaus.org/browse/MNG-1797
> Project: Maven 2
> Type: Bug
> Versions: 2.0.1
> Reporter: David Hawkins
> Attachments: MNG-1797-maven-project.patch
>
>
> If you specify ANY dependency excludes, all dependencies after that one in
> the pom will also exclude what you specified. They appear to be cumulative
> on every dependency in that they bleed over into sibling dependencies.
> It's easy to test if you add an exclusion to a random dependency. This
> exclusion should exclude a required transitive dependency that is included by
> a dependency lower in the list. You will find that the dependency lower in
> the list no longer includes the required dependency because it is using the
> filter you declared in the other 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
