ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stan towianski (JIRA)" <>
Subject [jira] Commented: (IVY-983) exclude does not work in non-trivial conf case
Date Mon, 03 Jan 2011 19:01:00 GMT


stan towianski commented on IVY-983:

One general thing we figured out is that if you have a circular dependency, excludes will
not work.
I do not know if that is for all excludes or not. If you have A depends on B,   and B depends
on C,  and C depends on A,
then we had excludes that did not work. When we fixed the circular dependency, the exclude
started working,
in this case for some apache-cxf -> geronimo_something jar.

You can find circular dependencies with something like tattletale.jar

I thought I read somewhere that excludes were supposed to happen last, though I did not find
it just now,
but there must be something in ivy in the case above that will keep excludes from working.

This happened in ivy-2.1.0 and ivy-2.2.0

> exclude does not work in non-trivial conf case
> ----------------------------------------------
>                 Key: IVY-983
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0-RC2
>         Environment: Ubuntu, Linux
>            Reporter: Benjamin Damm
>            Assignee: Nicolas Lalevée
>            Priority: Critical
>             Fix For: 2.1.0-RC2
> 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.

View raw message