Dominique Devienne wrote:
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
YesYesYes pleeeeease :-)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12024
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
