Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 7795 invoked from network); 20 Jun 2002 09:39:18 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Jun 2002 09:39:18 -0000 Received: (qmail 13112 invoked by uid 97); 20 Jun 2002 09:39:29 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 12993 invoked by uid 97); 20 Jun 2002 09:39: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 12900 invoked by uid 98); 20 Jun 2002 09:39:28 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <00cf01c2183e$5a7b1550$6401a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: <20020620073723.4388.qmail@icarus.apache.org> Subject: Docs out of sync Date: Thu, 20 Jun 2002 05:39:19 -0400 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: > I've realised that we now have a synchronisation problem; as soon as 1.5 goes out the door, we should really migrate to xdoc based docs ASAP. Yes, the more I've compared side-by-side the setters to our actual docs the more I cringe. We've got lots of issues in this realm where some attributes exist in code but are not documented (this is on purpose in some cases). We have cases where we are subclassing a task and then turn around and unsupport lots of its setters by throwing a BuildException in the setter - when what really should be done is refactor the common stuff out and allow subclasses to really be subclasses and not some weird partial support of the parent functionality. After 1.5 we can really start comparing what xdocs generates and try out the migration to it. The main dilemma is how to auto-generate or merge in the rich type of information we have in our HTML files where some attributes are allowed if others are specified and the complex interactions between attributes that exists in the code and is easily described in free-form text but not so easy to auto-generate. Erik -- To unsubscribe, e-mail: For additional commands, e-mail: