And <java>/<junit> as well please, so one can say
<propertyset id="runtime properties">
...
<propertyset>
<java>
<syspropertyset refid="runtime properties" />
</java>
<junit>
<syspropertyset refid="runtime properties" />
</junit>
Currently, I have to use entity include to achieve the same thing, and since
the element name is <sysproperty> for <java>/<junit>, but <property>
for
<ant>, and <param> for <antcall>, entity include doesn't even work!!!
<ant>
<propertyset refid="runtime properties" />
</ant>
<antcall>
<paramset refid="runtime properties" />
</antcall>
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.
Strangely enough, the same applies to <envset> for <exec> / <apply> / <java
fork="true"> / <junit fork="true">... --DD
-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]
Sent: Friday, December 13, 2002 9:10 AM
To: ant-dev@jakarta.apache.org
Subject: Re: Setting multiple properties in one condition
On Sat, 14 Dec 2002, Conor MacNeill <conor@cortexebusiness.com.au>
wrote:
> Thoughts?
You could have used Dominique's or Diane's ideas 8-)
+0.4
Now, if you add ids to the <propertset>s and make them refid-able in
<ant> and <antcall> and make them definable outside of <condition> as
well ... +1
Stefan
--
To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|