Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 26381 invoked by uid 500); 5 Oct 2001 10:25:03 -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 26363 invoked from network); 5 Oct 2001 10:25:03 -0000 From: "Kevin Jones" To: "Ant-Dev" Subject: Optional tasks Date: Fri, 5 Oct 2001 11:22:28 +0100 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Importance: Normal X-OriginalArrivalTime: 05 Oct 2001 10:24:06.0679 (UTC) FILETIME=[DD004270:01C14D87] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N How does ant 'know' about the optional tasks? Are they defined as part of the Ant core? For example if I use the JUnit task Ant picks the taskdef directly from options.jar (or whatever this releases jar file is called. But if I create my own task I have to put a taskdef in my build.xml file, even if I put the jar file containing the task into ant\lib. I was wondering where the optional task magic comes from? Kevin Jones Developmentor www.develop.com