Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 94047 invoked from network); 27 Oct 2000 15:16:20 -0000 Received: from public.ndh.net (HELO public.ndh.com) (195.94.90.21) by locus.apache.org with SMTP; 27 Oct 2000 15:16:20 -0000 Received: from sbodewig.bost.de ([195.227.98.11]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id RAA00035 for ; Fri, 27 Oct 2000 17:16:18 +0200 (MET DST) Received: (from bodewig@localhost) by sbodewig.bost.de (8.9.3/8.9.3) id RAA02073; Fri, 27 Oct 2000 17:16:18 +0200 X-Authentication-Warning: sbodewig.bost.de: bodewig set sender to bodewig@bost.de using -f To: ant-dev@jakarta.apache.org Subject: Re: reassigning perperty values? References: From: Stefan Bodewig Date: 27 Oct 2000 17:16:17 +0200 In-Reply-To: Gottfried Szing's message of "Fri, 27 Oct 2000 16:45:33 +0200 (CEST)" Message-ID: Lines: 40 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >>>>> "GS" == Gottfried Szing writes: GS> But there is no way to define an explicit override. This is what I said, we probably need a way to say it is OK to override this. IMHO the master build has to decide which are allowed to be overriden and not the sub build. Your example is very simple to solve BTW: GS> GS> GS> GS> GS> GS> GS> what you want is which is a lot easier to understand IMHO. And then as a short term solution (until we have decided on the future of properties) you can write your own task, say mutableproperty that does the same as but doesn't check whether the property already exists. You can always call Project.setProperty, it's just that doesn't want to override properties. Stefan