[
https://issues.apache.org/jira/browse/IVY-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916228#action_12916228
]
stan towianski commented on IVY-983:
------------------------------------
my ivy.xml file (parts):
<conf name="default" description="default"/>
<conf name="provided" description="used to specify that jar is
already provided within environment"/>
<conf name="runtime" description="used for runtime"/>
<conf name="test" visibility="private" description="used for
testing"/>
<dependency org="org.apache" name="log4j" rev="1.2.16"
conf="provided->default">
<exclude module="jmxtools"/> <- these 2 don't matter
<exclude module="jmxri"/>
</dependency>
<exclude module="log4j"
conf="runtime"/>
or
<exclude org="org.apache" module="log4j" conf="runtime"/>
<exclude module="log4j"/> <-- keeps it out of 'provide', but
it still showed up in 'runtime'
These 2 still pull down log4j-1.2.16.jar into libDir\runtime
<ivy:resolve file="ivy.xml" conf="runtime" />
<ivy:retrieve file="ivy.xml" conf="runtime"
pattern="${libDir}/[conf]/[artifact]-[revision].[ext]" />
[ivy:resolve] :: Ivy 2.1.0 - 20090925235825 :: http://ant.apache.org/ivy/ ::
This bug stills seems to be there.
> exclude does not work in non-trivial 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
> 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.
