ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Berry <>
Subject RE: criticism: property handling (here: no overwrite)
Date Wed, 13 Jun 2001 13:25:35 GMT
Conor hit the nail on the head. There are times when the path needs to
contain items which do not yet exist. In my case, this is actually dependent
on a Task firing -- I unpack different "distributions" which exist initially
as TAR.GZ files. 

Ideally I want a single <path> defined (my Classpath) -- at the top of the
file -- which is used by reference in several Tasks. (The ol' Don't Repeat
Yourself rule again ;-). But that isn't possible right now because the
<path> element is evaluated up-front (and croaks). A lazy evaluation would
fix my situation.

Thanks for listening,
-- Chris

> -----Original Message-----
> From: Stefan Bodewig []
> Sent: Wednesday, June 13, 2001 2:15 AM
> To:
> Subject: Re: criticism: property handling (here: no overwrite)
> Conor MacNeill <> wrote:
> > It would be nice if the path didn't evaluate the fileset until it
> > needed to supply the path so that paths based on jars in a fileset
> > where the jars don't yet exist can be used (if you know what I mean)
> You can do that now to a certain extent - just don't define the path
> until the jars have been created.
> For more than that, one would probably even need a way to refresh a
> path after jars have been added or removed - I'm not sure I'd want to
> go that far.
> Stefan

View raw message