Sanity check: framework Properties overriding build.properties at (Ant) build time?
Sanity check: framework Properties overriding build.properties at (Ant) build time?
- Subject: Sanity check: framework Properties overriding build.properties at (Ant) build time?
- From: Paul Hoadley <email@hidden>
- Date: Wed, 28 Oct 2009 15:44:31 +1030
Hello,
This may be completely normal, but I haven't run into it before.
I have a framework with a Resources/Properties file that contains a
particular property, say "foo=bar". I have an app that is dependent
on that framework. In the app's build.properties, it happens that I
have a coincidentally identical property name, say "foo=baz". In my
slightly modified build.xml (which imports the standard WOLips
build.xml and just overrides a few things), I use that foo property,
expecting it to have value 'baz', but it has value 'bar'. 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?
It's easily fixed, I've just removed the name collision. But if
that's the explanation, I didn't know that was happening.
--
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