Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 25972 invoked from network); 8 Feb 2002 00:06:10 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Feb 2002 00:06:10 -0000 Received: (qmail 19313 invoked by uid 97); 8 Feb 2002 00:06:12 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 19293 invoked by uid 97); 8 Feb 2002 00:06:12 -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 19282 invoked from network); 8 Feb 2002 00:06:11 -0000 From: "Conor MacNeill" To: "Ant Developers List" Subject: RE: Speaking of deprecation... Date: Fri, 8 Feb 2002 11:13:56 +1100 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: <067c01c1b034$3b2d5860$514bd6d1@compaq> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Magesh, I think you missed Bruce's point. Consider this scenario: You are given a build file. It uses some deprecated features. You are asked to bring it up to date. If the documentation doesn't specify what the deprecated features do, how can you confidently make the changes. I agree with Bruce. Documentation should reflect the code. If a feature is in the code, it should be in the documentation If a feature is deprecated in the code, it should be marked as deprecated in the documentation but it should still be described. Conor > -----Original Message----- > From: Magesh Umasankar [mailto:umagesh@apache.org] > Sent: Friday, 8 February 2002 11:05 AM > To: Ant Developers List > Subject: Re: Speaking of deprecation... > > > From: "Bruce Atherton" > > > And forcing someone to build a system that > > uses a feature in order to find out that > > feature is deprecated strikes me as badness. > > That is the general idea, I think - to make > it as tough to use deprecated attributes/tasks > as possible :-) > > > > > Then there is the question of learning how > > ant works by reading other people's build files. > > If the build files work and you can't figure > > out how they work by reading the documentation, > > that can be a frustrating experience for a new > > user (who may not recognize the significance > > of the deprecation warnings when they come up). > > They will work, but show up with big 'DEPRECATED' > warnings at runtime. That would convey the message > to the user pretty clearly, IMO. > > Cheers, > Magesh > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: