Hi Stefan,

First of all i would like to  thank you for your interests on our patch.

I'm currently trying to switch to trunk Head revision and i'm getting some
troubles with "nested inclusion".

I think that using "<include>" should allow user to have nested prefix, here
is a short example:
<project name="abstract">
<target name="myAbstractTarget" description="i'm abstract">
...
</target>
</project>

<project name="A">
<include file="abstact" as="myPrefix"/>
<target name="mySpecificTargetFromA" depends="myPrefix.myAbstractTarget"
description="i'm A">
...
</target>
</project>


<project name="B">
<include file="A" as="iLikeNestedPrefix"/>
<target name="mySpecificTargetFromB"
depends="iLikeNestedPrefix.mySpecificTargetFromA" description="i'm B">
...
</target>
</project>

<project name="generic build>
<extends file="B"/>
</project>

By typing ant -p i should see something like :
B.mySpecificTargetFromB --> i'm  B
B.iLikeNestedPrefix.mySpecificTargetFromA --> i'm A
B.iLikeNestedPrefix.myPrefix.myAbstractTarget --> i'm abstract

In our previous patch it was done by ImportTask (
http://easyant.abrm.info/trac/browser/trunk/src/main/patches/ant-697121-easyant-patch.diffl168->l187)
What do you think about it?

In addition to this, could it be possible to have a parametrized prefix
separator? I guess you've added a "." betwen prefix and target name (ex:
myPrefix.myTarget), could we have something more flexible?
In EasyAnt, we currently don't want to have a prefix separator, by
conventions our public target are prefixed with ":" and our private target
are prefixed with "-".

Thanks in advance for your feedback.


2008/11/11 Stefan Bodewig <[EMAIL PROTECTED]>

> On 2008-11-10, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> > Right now I'm pretty close to simply add an "as" attribute to import,
> > add "include" as an alias name for import and make the task behave
> > differently when it is called as include.
>
> Done.
>
> The implementation differs from EasyAnt's and we don't have phases
> (yet?), so Jean-Lousi or Xavier should either modify the patch or tell
> people to now use Ant trunk more recent than 713006.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to