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.
So I tried to go the other way and change to "include.xxx" properties along with <target name="xxx" if="include.xxx"> : this works just fine if I put "include.xxx=" in local.build.properties without changing build.properties.
fixed it for me introducing: <property file="blocks.properties"/> <condition property="unless.exclude.XXX"> <istrue value="${exclude.XXX}"/> </condition>
and using <target ... unless="${unless.exclude.XXX}">
this way you can set exclude.XXX in your local.build.properties to true, or false as you like it.
Good idea !
However, I think it's not applicable for block excludes since it would require to change the build file for each new block. Or can we generate automatically a set of exist/not-exist properties from a set of true/false properties (custom task, XSLT, etc ?).
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
