Problem with wildcards in defaultconf attribute
-----------------------------------------------
Key: IVY-1306
URL: https://issues.apache.org/jira/browse/IVY-1306
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0
Environment: Windows XP, Java 6, ant 1.8.2
Reporter: Marc De Boeck
Priority: Minor
In the ivy.xml file of a module, I have the following configurations and
dependencies:
<configurations>
<conf name="compile"/>
<conf name="test" extends="compile" />
<conf name="rad" />
<conf name="ear" />
<conf name="wsdl"/>
</configurations>
<dependencies defaultconfmapping="* -> #" defaultconf="*,!wsdl" >
<dependency org="org1" name="mod1" conf="wsdl -> conf1"
rev="latest.integration" />
<dependency org="org1" name="mod2" rev="latest.integration" />
</dependencies>
mod1 and mod2 have the same configurations as the parent module above.
In the build file, I do the following to resolve and retrieve the artifacts for
this parent module:
<ivy:resolve conf="ear" />
<ivy:retrieve pattern="${project.target.lib.dir}/[artifact].[ext]"
sync="true" conf="ear"/>
<ivy:report conf="ear" ... />
It seems that for modules such as mod2, I retrieve artifacts from all
configurations (except the conf "wsdl") and not just the ear-configuration.
The attribute "defaultconf" seems to be responsible for that.
This can also be seen in the output of ivy:report.
For mod2, I can see that it returns the following configurations:
Configurations: test, compile, rad, ear, *
When I change the defaultconf attribute to:
<dependencies defaultconfmapping="* -> #" defaultconf="compile,rad,ear" >
Then the resolve works as expected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
