environment variables and substitution into properties

[Clayton Cramer]

If you define a property that includes ${ENV[varname]}, when you call getProperty for that property, it will substitute the environment variable varname in place of the ${ENV[varname]}. At least, it does it when I run on Windows. But when I run on Suse Linux 11, it does not: ${ENV[varname]} remains in the property string, with no substitution. I can see the environment variable present in bash--but the substitution does not take place when I retrieve the property. Any suggestions where to start looking?

[Campbell Ritchie]

Don’t know. Sorry. But not amongst us beginners who frequent this area of cyberspace, so I shall move this thread.

[Winston Gutkowski]

Clayton Cramer wrote:If you define a property that includes ${ENV[varname]}, when you call getProperty for that property, it will substitute the environment variable varname in place of the ${ENV[varname]}. At least, it does it when I run on Windows. But when I run on Suse Linux 11, it does not: ${ENV[varname]} remains in the property string, with no substitution. I can see the environment variable present in bash--but the substitution does not take place when I retrieve the property. Any suggestions where to start looking?

Like Campbell, I was completely unaware of such a construct in Java (and I see no reference to it in the java.util.Properties documentation - version 6, at least).

Perhaps you could explain where this definition comes from?

Winston

[Campbell Ritchie]

I tried googling and found this, which seems to be related to Ant.

[Winston Gutkowski]

Campbell Ritchie wrote:I tried googling and found this, which seems to be related to Ant.

Cheers mush.

Winston