Sylvain Wallez wrote:
Martin Holz wrote:

Stefano Mazzocchi <[EMAIL PROTECTED]> writes:



Martin Holz wrote:


Stefano Mazzocchi <[EMAIL PROTECTED]> writes:



The new build system has landed on CVS.

[...]


read BUILD.txt
cp blocks.properties local.blocks.properties
cp build.properties local.build.properties
[modify the local copies as you like, leaving the original intact]
build webapp [this will generate the webapp]

Does overriding boolean properties work? If I set
"exclude.webapp.samples=false"
in local.build.properties a target like <target
name="prepare-webapp-samples" depends="package-samples"
unless="exclude.webapp.samples"> won't be executed. "unless" does
not test, if the variable has the value of "true" or "false".
It tests, if the value is defined. At least, that's what the
documentation for ant 1.5 says.
The only way to execute the target is removing the definition from
local.build.properties
and build.properties. The result will be failed build, but that's a other story.

You don't have to set things to false, you have to uncomment them!


In local.build.properties? This would not help, since they
are defined in build.properties, which is read by build.xml
immediately after local.build.properties. You would have to uncomment them in build.properties.


Martin



Failed on the same problem today. For those targets that we want to exclude in the default build, having a "exclude.xxx=true" in build.properties requires to modify this CVS-managed file to allow building "xxx", which obviously isn't good.

the exclude.* stuff that is not commented out in the build.properties will be in the future so the problem goes away.



Reply via email to