[
https://issues.apache.org/jira/browse/IVY-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631976#action_12631976
]
Maarten Coene commented on IVY-820:
-----------------------------------
I don't think your code snippets illustrate a bug. The excludeRule must know
from which configurations it must exclude the artifact. So, it seems logical to
me that your first example won't work. For your second example, "*" is not a
configuration, so it doesn't work as well.
I still couldn't reproduce the original problem where the exclude is defined in
an ivy.xml file.
> Global Exclusions Fail to Work Transitively
> -------------------------------------------
>
> Key: IVY-820
> URL: https://issues.apache.org/jira/browse/IVY-820
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Environment: Java 6
> Reporter: Julian
>
> When declaring a global exclusion, the module is excluded only from locally
> declared dependencies, and not their transitive dependencies. The only way
> to exclude a module from an entire project, is to declare the exclusion
> locally for every dependency that either directly, or through a transitive
> dependency, relies on the module. A detailed explanation of this issue can
> be found on the mailing lists here (first two posts explain the issue more
> thoroughly):
> http://www.nabble.com/Global-and-Local-Excludes-Being-Ignored-By-Ivy--Config-Prblm-of-Bug---td17262577.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
