Yes, this is what I had in mind with my statement below: By having this <propertyset>, which would need mechanism to *pull in* existing properties within it (using a prefix or regex match on the property name I guess), one could streamline the property/sysproperty/param passing to quite a few tasks.
Namely, I thought of: <propertyset id="junit-stuff1" pattern="junit.*" /> <propertyset id="junit-stuff2" prefix="junit." /> The latter is of course a subset of the former, but we have prefix attributes in other tasks as well (although only the former is really necessary). Is any one planning on really working on that? If not, I could look into it as well, provided we have enough consensus this time, it would be a worthy addition (does that need a vote?)... --DD -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Saturday, December 14, 2002 1:24 PM To: Ant Developers List Subject: Re: Setting multiple properties in one condition I'd like to be able to define a propertyset from a pattern then. <propertyset id="junit-stuff" pattern="junit.*" /> to pass down stuff that is defined, and not the stuff that is undefined... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
