Return-Path: 
 <ant-dev-return-14252-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 94723 invoked by uid 500); 1 Jun 2001 10:00:35 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 94537 invoked from network); 1 Jun 2001 10:00:33 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: ant-dev@jakarta.apache.org
Subject: Re: Configure->Template->Build
References: <Peter Donald's message of "Thu, 31 May 2001 01:31:03 +1000">
	<3.0.6.32.20010530133850.008abcf0@mail.alphalink.com.au>
	<3.0.6.32.20010531013103.008c6680@mail.alphalink.com.au>
	<3.0.6.32.20010531205243.008ce100@mail.alphalink.com.au>
From: Stefan Bodewig <bodewig@apache.org>
Date: 01 Jun 2001 12:00:40 +0200
In-Reply-To: Peter Donald's message of "Thu, 31 May 2001 20:52:43 +1000"
Message-ID: <m3zobsldtj.fsf@bodewig.bost.de>
Lines: 31
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Peter Donald <donaldp@apache.org> wrote:

> At 12:02 PM 5/31/01 +0200, Stefan Bodewig wrote:
>>
>>So don't define the compile target in that thing you include with
>>projectref at all and provide this single target in all 17 build
>>files (as they all seem to be different anyway)?
> 
> And loose maintainability.

Why so? All targets that are the same are in the shared file while all
that are different will be maintained independently - or they are not
that different at all 8-)

> What happens when you need to modify how javac works

modify in what way? debug/deprecation and friends? User preferences.

> or worse the order of tasks.

For all build files in the same way? So refactoring them to have a
common target that contains exactly those tasks seems appropriate.

> That would mean you are relegated to modifying 17 build files -
> completely defeats the point of having templating don't you think ;)

If this was true, yes.

How would your configuration/templating aproach deal with this?

Stefan