Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 23070 invoked by uid 500); 26 Feb 2003 12:42:03 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 23056 invoked from network); 26 Feb 2003 12:42:03 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 26 Feb 2003 12:42:03 -0000 Received: (qmail 27513 invoked from network); 26 Feb 2003 12:42:00 -0000 Received: from unknown (HELO apache.org) (stefano@80.105.91.155) by pulse.betaversion.org with SMTP; 26 Feb 2003 12:42:00 -0000 Message-ID: <3E5CB635.1010909@apache.org> Date: Wed, 26 Feb 2003 13:42:29 +0100 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030202 X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: The new build system References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Morrison, John wrote: >>From: Martin Holz [mailto:holz@fiz-chemie.de] >>Stefano Mazzocchi writes: >> >> >>>Martin Holz wrote: >>> >>>>Stefano Mazzocchi 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 >>>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. > > > No, that's not how ANT works. > > Follow the instructions and *TRY* them before emailing! John, Martin is totally right. You can't 'de-comment' something by overloading and setting it to true or false will still make ant failing since the except="" attribute will work based on the existance of that property, not its value. But even more important, watch your tone! Martin was trying to help and even if he was wrong, he still deserves your respect. -- Stefano Mazzocchi Pluralitas non est ponenda sine necessitate [William of Ockham] --------------------------------------------------------------------