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 1136 invoked from network); 15 Dec 2000 19:36:27 -0000 Received: from cx36961-b.chnd1.az.home.com (HELO ?24.16.142.11?) (24.16.142.11) by locus.apache.org with SMTP; 15 Dec 2000 19:36:27 -0000 Received: from [192.0.1.63] by 24.16.142.11 (AppleShare IP Mail Server 6.2.1) id 42089 via TCP with SMTP; Fri, 15 Dec 2000 12:36:28 -0700 Mime-Version: 1.0 X-Sender: Subscriber@alice.gloaming.com Message-Id: Date: Fri, 15 Dec 2000 12:36:17 -0700 To: ant-dev@jakarta.apache.org From: James Bucanek Subject: init targets Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N So many questions... The documentation talks about "init" targets. On first reading, it appeared that 'init' was a reserved target that would always get executed first. I guess I was mistaken. It now appears that a so-called init target is simply a target that all other targets depend on. Which means I have to ensure that the correct 'depends' attribute is set for every single target in my project or things won't work. :( So, is anyone contemplating defining a target, or a target attribute, that causes a target to always get executed before any other target(s)? Currently, my solution is to write some special code to automatically add the 'init' target dependency to every other target before I start the build. __________________________________ James Bucanek