Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 53136 invoked from network); 27 Feb 2002 07:43:58 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 63.251.56.142 with SMTP; 27 Feb 2002 07:43:58 -0000 Received: (qmail 11987 invoked by uid 97); 27 Feb 2002 07:44:03 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 11925 invoked by uid 97); 27 Feb 2002 07:44:02 -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 11868 invoked from network); 27 Feb 2002 07:44:02 -0000 From: "Adam Murdoch" To: "Ant Developers List" Subject: RE: XDocs Proposal Date: Wed, 27 Feb 2002 17:41:30 +1000 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.2910.0) In-Reply-To: <035901c1bf51$b0fde510$6601a8c0@darden.virginia.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: 63.251.56.142 1.6.2 0/1000/N X-Spam-Rating: 63.251.56.142 1.6.2 0/1000/N > -----Original Message----- > From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] > Sent: Wednesday, 27 February 2002 3:44 PM > To: Ant Developers List; jakarta-ant-cvs@apache.org > Subject: XDocs Proposal > > > From: > > > ehatcher 02/02/26 21:25:36 > > > > Added: proposal/xdocs/src/org/apache/tools/ant/xdoclet > > AntSubTask.java AntTagsHandler.java > > Log: > > First pass at XDoclet generation of Ant task documentation. > > > Let me know if you spot any idiosyncracies in what it generates - > I've only > spot checked some things to make sure it was looking decent. I > wrapped all > possible XML breaking things in CDATA - maybe its better to encode strings > first? > > Anyway, have at it! I look forward to your feedback and improvements. > Wow. This is very cool. Some minor comments: * It looks like the template is picking up nested classes when generating the default.properties file. For example, there's a task called 'ant.reference' in there that points to class taskdefs.Ant. * I wonder if might be worth adding an (optional) @ant:description tag, which would take precedence over the comment. It might be useful at times to be able to add comments to a class or method, that don't end up in the user guide. * Should we add the equivalent of the user manual's "required" column somewhere? * I guess we need to handle the data types as well. Seems like it should be straight-forward enough. Adam -- To unsubscribe, e-mail: For additional commands, e-mail: