Dave Westerman wrote:
Oliver, thanks for the info. I am indeed using release 1.3. And you're
right, the $$ does escape the variable character, in some circumstances.
I didn't get much time to work on this today, but when I changed it to
only have one entry in the property that looks like a
Oliver, thanks for the info. I am indeed using release 1.3. And you're
right, the $$ does escape the variable character, in some circumstances.
I didn't get much time to work on this today, but when I changed it to
only have one entry in the property that looks like a variable, it works
okay:
Hi Dave,
Dave Westerman wrote:
I am using the commons-configuration for my property files. However,
unfortunately, I have a need to have a value in some of my properties
that look exactly like the variables that commons-config uses.
myproperty=${myNonCommonsConfigVariable}
I've tried to
I am using the commons-configuration for my property files. However,
unfortunately, I have a need to have a value in some of my properties
that look exactly like the variables that commons-config uses.
myproperty=${myNonCommonsConfigVariable}
I've tried to escape it thus:
