ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Goldspink (JIRA)" <>
Subject [jira] Commented: (IVY-983) exclude does not work in non-trivial conf case
Date Fri, 18 Sep 2009 15:03:16 GMT


Matt Goldspink commented on IVY-983:

I'm not sure this is fixed in 2.1.0-rc2 or perhaps not for the use case I'm looking for.

I have an Ivy file like:

<ivy-module version="1.0">

  <info organisation="matt" module="project2" revision="1.0.0"/>

    <conf name="war-runtime"/>
    <conf name="build-war" extends="war-runtime" visibility="private"/>

    <dependency org="matt" name="project1" rev="1.0" conf="war-runtime"/>

    <exclude org="javax.servlet" module="servlet-api" conf="war-runtime"  />



In this case project1 depends on the servlet-api dependency and transitively brings it into
project2. Now I want it to be excluded from my war-runtime but to be present on the build-war
configuration. However the above configuration seems to still bring down servlet-api. I've
tried various combinations of the above including explicitly declaring the dependency in this
file as build-war dependency, specifying the artifact name etc, but none seem to give me what
I want.  Should this be re-opened or another JIRA filed?

> 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