It seems like a bug to me. Please create a JIRA ticket.
I think it could be caused because your war configuration extends the default
configuration.
Could you try to modify your ivy.xml so that this isn't the case any longer and
try again?
Maarten
----- Original Message ----
From: Benjamin Damm <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, December 4, 2008 11:13:04 PM
Subject: Re: exclude doesn't seem to quite work?
I should add that this is 2.0.0rc2.
-Ben
On Wednesday 03 December 2008 05:16:22 pm Benjamin Damm wrote:
> Hi gang,
>
> 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.
>
> Am I doing something wrong here or is there something up with how <exclude>
> works?
>
> Thanks,
> -Ben
--
Benjamin Damm
Silver Spring Networks
650-298-4200 x201
