From ant-dev-return-26434-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Mon Feb 25 22:55:27 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 11740 invoked from network); 25 Feb 2002 22:55:26 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Feb 2002 22:55:26 -0000 Received: (qmail 16840 invoked by uid 97); 25 Feb 2002 22:55:29 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 16824 invoked by uid 97); 25 Feb 2002 22:55:29 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 16808 invoked from network); 25 Feb 2002 22:55:29 -0000 Message-ID: <028401c1be4f$7b363b10$6601a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: Subject: Re: @tags Date: Mon, 25 Feb 2002 17:55:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Jon Skeet" > So, plans: > o Add tag option to JavaDoc task (ignore if not using 1.4? Warning? I'm not up on the conventions here) Dunno. is a huge beast of a task. > o Add todo tag option to root build.xml (?) I am planning on doing this. I've actually got it ready to go. The question is: Where do I put xdoclet.jar? Or just leave it as an external dependency and use to fail the "todo" target gracefully if its not there? > o Learn where to use the new ant:task stuff before fixing up the tasks Don't worry about the @ant:task thing. I'll prototype it. Its actually going to be minimal work currently. I want to mimic Diane's categorization, so all tasks will have @ant:task category="..." at the very least. For a task name, I'm going to use an XDoclet tag handler (a custom tag for an XDoclet template) that will be smart about task names. Most task names are the lowercased version of their class name. For the exceptions (i.e. Exit.java) we'll add a name="..." to the @ant:task also. I've also added logic to strip a trailing "Task" from the class name if it exists (with @ant:task name="..." taking precedence) - I use the convention of Task.java personally, but that isn't really the Ant taskdefs convention. The biggest thing will be pulling the documentation from the HTML into the Javadoc comments for each attribute/element method, and we can do that gradually. I could even implement merge points in XDoclet to go out and fetch pieces from the HTML, although this is probably unnecessary work, as pulling it into Javadocs makes the most sense for attribute/element stuff. For the examples, I think merge points make great sense though, allowing them to be separate in cleaner syntax than HTML encoded Javadoc stuff. Erik -- To unsubscribe, e-mail: For additional commands, e-mail: