André Pilz <[EMAIL PROTECTED]> wrote:
> ...
> that is standard behaviour for ant. The first property definition wins.
> A simple solution for this example is to load the second property file
> first.
> ...
That's exactly how we do it.
We have a default configuration held in a properties file.
Yes that makes sense.
The problem would then be that if the property is empty in the first file
the second would not get its thing in the zone.
All that said I think I can workout something that doesn't allow empty
fields to be written at all.
And thanks for the clarification.
Regards,
-- wiz
Hello,
that is standard behaviour for ant. The first property definition wins.
A simple solution for this example is to load the second property file
first.
Also see the Task in ant-contrib, but I never needed it.
Cheers,
Andre
wizshah schrieb:
I have two following lines added to my build
