Indeed, it will certainly be useful.
Thanks a lot.
Patrick
On 9/7/07, Bruce Atherton <[EMAIL PROTECTED]> wrote:
> True, if your properties file has embedded ant properties that you
> expect to be replaced, what you will get back when you regenerate the
> file is not the property but the replacemen
True, if your properties file has embedded ant properties that you
expect to be replaced, what you will get back when you regenerate the
file is not the property but the replacement value. This is still useful
as a properties file, though, just not as maintainable as the original
would have bee
Actually, if you wanted to do it programatically in code and you could
guarantee that each line had no more than one token, you could probably
make it work by creating regular expressions. Here is some pseudocode:
for each line in the template file
pull out the token name from the lin
Hello,
I see what you mean and agree.
The worse case would be when we have something like
@prop1@@prop2@
in the template files
For the start of the property, I guess we can find it out in the
template (looking for the index of @). The end is much trickier.
Thank you anyway.
Patrick
On 9/6/07,
Hi,
-Original Message-
From: Patrick Martin [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 06, 2007 10:18 AM
To: Ant User
Subject: extract properties from file and corresponding template
/*
Hello,
I have a file that was generated from a template and a set of
properties using ant
