[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [dash-dev] commonbuilder - build.cfg generation order
|
First instance take precedence for <property name=x value=y/>, but it seems that in this case file is loaded using java.util.Properties.load() - so, the last instance wins.
The specific properties I was trying to set are compilerArg and projNamespace.
Regards,
Alex
On Sun, Mar 14, 2010 at 01:46, Nick Boldt
<nickboldt@xxxxxxxxx> wrote:
The file is read as Ant properties. Thus the first instance of a property trumps all others.
Because of this, the correct load order is your stuff, common stuff, default stuff... this allows you to override anything set as a default with your own customizations, while allowing defaults to exist so you don't have to set them if you don't need to.
Is there a specific problem that caused you to report this? Ie., is there a property that you're trying to set which isn't being correctly read/loaded? (It's possible there's a bug somewhere involving my use of <var> instead of <property>.)
N
On 03/13/2010 01:10 PM, Alexey Panchenko wrote:
Hi all,
I was trying to use commonbuilder and I've found an interesting issue:
build.cfg is generated in this order:
1. project build.properties
2. common build.propertes
3. server.properties
So, if I define the property in my project, it is overridden by common
properties.
Why is it generated in this order?
What do you think about loading project build.properties last?
(tools/scripts/buildAllHelper.xml file, line 2593)
Thank you,
Alex