> From: Matt Benson [mailto:[EMAIL PROTECTED] > > My reason for wanting to nest the propertyset into a > regular <env> element is that these are passed by > <exec> and <java (w/ forking)> to an Environment > object. This means that if the code is added to > Environment, so that: > > <exec executable="foo"> > <env> > <propertyset|whatever name we want here > refid="foo.properties" /> > </env> > </exec> > > Any user of Environment.Variable (exec should be the > paradigm) automatically supports propertysets. If > this nesting approach--with whatever element name, > although I tend to use the add(...) IH methods--is > acceptable in general, I have got this working > already.
I see your point Matt. Easy and painless to implement. From the user perspective though, it overloads the meaning of <env>, and departs from what was done with <sysproperty> + <syspropertyset>. So I'm not against your proposal, but I don't think it's the best UI for this feature. But since I'm just the talker and not the doer, it's your opinion and the community's as a whole that should prevail, not my own opinion. The feature itself may be more important than it's UI?! --DD ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
