exclude does not work in non-trival conf case
---------------------------------------------
Key: IVY-983
URL: https://issues.apache.org/jira/browse/IVY-983
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0-RC2
Environment: Ubuntu, Linux
Reporter: Benjamin Damm
I'm running into a problem with <exclude>... my ivy.xml looks like this:
<ivy-module version="2.0">
<info organisation="ssn-src" module="pc"/>
<configurations defaultconfmapping="default->default">
<conf name="default" />
<conf name="provided" description="they are provided by the
env." />
<conf name="compile" extends="default,provided" />
<conf name="war" extends="default"/>
</configurations>
<dependencies>
...
<dependency org="log4j" name="log4j" rev="1.2.14+"
conf="provided->default"/>
... <!-- other deps; indirect depends on log4j 1.2.13 in all my confs. -->
<exclude module="log4j" conf="war"/>
Now, log4j;1.2.14 is in my compile conf, as I expect it to be. But
log4j;1.2.13 appears in my war conf, which is not what I expect. I expect
there to be no log4j because in this case the environment will provide it
(jboss) with its own custom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.