Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 22143 invoked by uid 500); 26 Apr 2001 06:58:39 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 22116 invoked from network); 26 Apr 2001 06:58:39 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: [VOTE] The late stuff References: From: Stefan Bodewig Date: 26 Apr 2001 08:58:44 +0200 In-Reply-To: Stefan Bodewig's message of "26 Apr 2001 08:49:23 +0200" Message-ID: Lines: 35 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 > * Integration of the depends task and javac tasks Why, what's wrong with invoking two tasks in sequence? I usually have a pattern like this in my build files which makes it possible to compile without the depend task and only run it, if I know I'm going to need it (by using ant -Ddependprop=1). You only need to run if you've made changes to the interface, not the implementation of something, so running it all the time would be a pain. I don't need to mention, that recompiling everything using jikes would be faster than doing an extensive dependency check, as Pete will do that 8-) > * recursive property resolution( ie resolving ${dist.${name}.dir} ) Could I have a use case for this please - something real worldish, that you cannot (conveniently) solve be something other than that? Stefan