Re: xmlproperty not expanding

Hi Ronald, if you look at the manual for XmlProperty you will find the following statement: "By default, this load does *no* processing of the input. In particular, unlike the Property task , property references (i.e., ${foo}) are not resolved." Un

Re: taskdef defined in project or target

Generally speaking, one does not care about the memory usage of Ant unless you're working with a task that gets repeated a LOT. Just out of interest, I tried the two scenarios whilst tracing the class loader. Yes in the case where the taskef is inside a target, the class gets loaded later. But

Re: Set an env variable?

This is a limitation of Java rather than Ant. See this article for a bit more information: http://stackoverflow.com/questions/318239/how-do-i-set-environment-variables-from-java I'd recommend that you keep a list of environment variables you care about as properties. When you call it has a parame

Re: Build directly on machine vs. SSH to machine and start build

I ended up writing a custom ant task to do this. Unfortunately in both *nix and windows you can't always rely on environment variables. On *nix you need to read the output of /bin/hostname or on windows read the output of WScript.Network.ComputerName Regards, Simon On 8/05/2012, at 8:28 AM, E