ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject RE: <script> and bsf
Date Tue, 10 Dec 2002 20:00:48 GMT
Dominique Devienne wrote:

> I agree with you Alexey. Even if the current behavior seems weird, it's
> Ant behavior, which many people take advantage of, including me, to create
> 'property setting' targets (properties used by other targets specified on
> the command line). I don't want that behavior to go away (that would be a
> clear regression, which I don't expect from Costin).

So you rely on the common targets being executed twice ? 

How will that affect the property setting targets ? 

I have no problem with keeping this behavior - and if people relly
on it then it may even be usefull :-)

Probably documenting it clearly is the best solution ( including the use 
case you describe - so people who don't get it, like me, can use it )

Regarding comma-separated targets - sounds good, but I would like to 
know the use case. I don't feel very well about adding much logic to
the command line - and I'm not sure how this will affect the API.


> I like Alexey's idea of comma-separating targets names on the command line
> to have the pseudo-target behavior, similar to the current 'depend'
> attribute of <target>. --DD
> -----Original Message-----
> From: Alexey Solofnenko []
> Sent: Tuesday, December 10, 2002 12:55 PM
> To: 'Ant Developers List'
> Subject: RE: <script> and bsf
> It is a feature, but many people would like to have it implemented
> differently. Without breaking existing functionality I think it is
> possible to add "ANT A,B" syntax to execute A and B without reexecuting
> common targets, by creating a temporary pseudo target that depends from A
> and B and executing it.
> - Alexey.
> -----Original Message-----
> From: Costin Manolache []
> Sent: Tuesday, December 10, 2002 10:32 AM
> To:
> Subject: Re: <script> and bsf
> Stefan Bodewig wrote:
>>> - should "ant A B" behave like "ant A; ant B" or remove duplicated
>>> targets ?
>> It does neither of both.  It will execute common targets twice (so
>> it's close to ant A; ant B), but properties set during the first pass
>> will keep their value in the second pass - same for references.
> That sounds like a clear bug that needs to be fixed.
> ...

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message