ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc De Boeck (JIRA)" <>
Subject [jira] [Created] (IVY-1306) Problem with wildcards in defaultconf attribute
Date Sun, 17 Jul 2011 20:11:00 GMT
Problem with wildcards in defaultconf attribute

                 Key: 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:

      <conf name="compile"/>
      <conf name="test" extends="compile" />
      <conf name="rad" />
      <conf name="ear" />
      <conf name="wsdl"/>
    <dependencies defaultconfmapping="* -> #" defaultconf="*,!wsdl" >
        <dependency org="org1" name="mod1" conf="wsdl -> conf1" rev="latest.integration"
        <dependency org="org1" name="mod2" rev="latest.integration" />
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

            <ivy:resolve conf="ear" />
            <ivy:retrieve pattern="${}/[artifact].[ext]" sync="true"
                        <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:


View raw message