ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: overriding included configurations
Date Wed, 15 Nov 2006 12:27:40 GMT
On 11/15/06, Steve Loughran <stevel@apache.org> wrote:
>
> Imagine I have some configurations
>
> <configurations defaultconfmapping="default">
>    <conf name="default" extends="master,runtime"/>
>    <conf name="compile" visibility="private"
>        description="artifacts needed to compile the application"/>
>    <conf name="unittest" extends="compile"
>        description="the classpath needed to run unittests"/>
>    <conf name="systemtest" extends="compile"
>        description="the classpath needed to run systemtests"/>
>    <conf name="test" extends="unittest,systemtest"
>        description="the classpath needed to run tests"/>
>    <conf name="master" description="contains the artifact but no
> dependencies"/>
>    <conf name="runtime" description="runtime but not the artifact"/>
> </configurations>
>
> Then I include them
>
>
> <configurations>
>   <include file="../standard.xml" />
> </configurations>
>
> Can I override an included configuration, giving it different extensions?
>
>    <conf name="unittest" extends="jaxb" />
>    <conf name="systemtest" />


This is not intended to work, but I think it does :) Give it a try, but
since configurations are stored in a Map by name and no verification is
done, the new definition should replace the old one.

Xavier

-Steve
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message