Re: Sanity check: framework Properties overriding
Re: Sanity check: framework Properties overriding
- Subject: Re: Sanity check: framework Properties overriding
- From: Paul Hoadley <email@hidden>
- Date: Thu, 29 Oct 2009 14:07:57 +1030
Hi Susanne,
On 29/10/2009, at 12:11 AM, Susanne Schneider wrote:
I've been trapped by this too. In contrast to normal programming
behaviour ant works the other way round: the first setting a
property will win. Once a property is set it cannot change to
anything else! Properties are no variables, see the ant manual for
this.
Thanks for the reply. If I ever knew that about Ant, I had forgotten
it.
In any case, the bit that surprised me was that all the Resources/
Properties files were being read by Ant at build-time at all. I
suppose I had always assumed they were strictly run-time properties,
but here they are being read at build-time as well? If that's really
what I was seeing, maybe I'm just the only person on the list
surprised by it.
Am I just imagining it, or are the properties in the framework's
Resources/ Properties file being imported by Ant as build
properties, and are they overriding the definitions in the app's
build.properties?
So the second part of that question is answered by Susanne: yes,
because with Ant it's "first definition wins".
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden