> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > On Mon, 9 May 2005, Matt Benson <[EMAIL PROTECTED]> wrote: > > Variable can accept a nested PropertySet OR have its > > key & value attributes set as usual > > > > I wonder about the feeling of the dev community on such a > > change... ? > > Works for me, although we better use a different name than propertyset > in the user-visible part. <variableset>? I've never been good at > names, but using "property" in the context of environment variables > feels wrong.
I also think this is a good idea (I was always too lazy to do it.) As far as names are concerned, I'd go with the same name already used by the task with a 'set' suffix, i.e. for <java>/<junit>/<exec>, use <envset>. With <syspropertyset> and <envset>, both using a mapper with a prefix, you can then easily configure the runtime environment of <junit> for example, without changing the build script, by defining properties (easily done in a user-specific way) like runtime-env.SOME_ENV_VAR and runtime.SOME_PROPERTY. --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]
