Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 53019 invoked by uid 500); 21 Jun 2003 18:36:38 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 53006 invoked from network); 21 Jun 2003 18:36:37 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.232.157) by daedalus.apache.org with SMTP; 21 Jun 2003 18:36:37 -0000 Received: from 66-44-91-214.s595.tnt5.lnhva.md.dialup.rcn.com ([66.44.91.214] helo=geoff2k) by host.leverageweb.com with asmtp (Exim 3.36 #1) id 19TnBA-0007jv-00 for cocoon-users@xml.apache.org; Sat, 21 Jun 2003 14:33:37 -0400 From: "Geoff Howard" To: Subject: RE: I may be wrong but... Date: Sat, 21 Jun 2003 14:57:41 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - xml.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N You are right that properties in ant once set are not modified. If you look carefully the values that depend on any value are commented out in build.properties - uncommenting them in your local copy will accomplish exactly what is meant. Also notice the order in which the properties are read: So, the cocoon.build.properties in your homedirectory is loaded first, then the local.build.properties, then build.properties. The first one to set the value wins, and Cocoon gives you two shots at them before the default apply. HTH, Geoff > -----Original Message----- > From: Richard Doust [mailto:rdoust@comcast.net] > Sent: Saturday, June 21, 2003 1:45 PM > To: cocoon-users@xml.apache.org > Subject: I may be wrong but... > > > I'm not certain I'm right, but I have the sneaking suspicion that > the build > the way it's written right now cannot possibly work. As far as I know, > there's no way to unset a property in ant. The "unless" attribute of a > target will not build the target if the property is "set". As far as I can > see, this means if it has any value at all. The only way to > overcome this is > to modify build.properties to remove the setting of those property values. > It cannot be overridden by copying build.properties to > local.build.properties and modifying that as suggested because it's not > possible to define them to a non-value. > I have commented those properties out of build.properties (and > local.build.properties) and this has solved my problem. > That's my two cents worth. > Rich > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org > For additional commands, e-mail: cocoon-users-help@xml.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org