From ant-dev-return-20543-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Thu Nov 29 21:35:03 2001 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 68527 invoked from network); 29 Nov 2001 21:35:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Nov 2001 21:35:03 -0000 Received: (qmail 26466 invoked by uid 97); 29 Nov 2001 21:28:46 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 26451 invoked by uid 97); 29 Nov 2001 21:28:45 -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 26438 invoked from network); 29 Nov 2001 21:28:45 -0000 Message-Id: <5.1.0.14.0.20011130101619.00acd910@actwelsvr14> X-Sender: bevan.arps@actwelsvr14 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 30 Nov 2001 10:25:21 +1300 To: "Ant Developers List" From: Bevan Arps Subject: Re: removing deprecated stuff In-Reply-To: <000f01c17917$4b55afc0$e241d6d1@compaq> References: <6303CA4AFB63D4119B9C00D0B73E8CAC2FFD1C@relay06-b.indigo.ie> <5.1.0.14.0.20011130084209.00ac3610@actwelsvr14> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_3981645==_.ALT" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=====================_3981645==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I wrote: > I'd suggest going the other way: > ONLY support deprecated features when run with a -legacy flag. Magesh responded: > The user would always run ant using -legacy turned on without > caring to upgrade tasks? Quite possibly - the idea here, though, is that the user has to explicitly decide to use the flag to get access to deprecated features. This avoids the "problem" of people using features and not realizing they are deprecated. The messages could also include "hints" to point people in the right direction. One implementation could be to give errors without the flag, and warnings with. Behaviour could be something like this. Without the flag: Error: is deprecated and should be replaced with . Error: See http://jakarta.apache.org/ant/upgrading.html for details. BUILD FAILED With the flag: Warning: Deprecated features are used in this build. Warning: This build file should be updated to avoid using these features. ... Warning: is deprecated and should be replaced with . Warning: See http://jakarta.apache.org/ant/upgrading.html for details. ... Just my 2c, Bevan. -- "Programming is an Art Form that Fights Back" Bevan Arps (bevan.arps@actfs.co.nz) Senior OO Analyst, ACT Financial Systems This communication is confidential to ACT Financial Systems (Asia Pacific) and is intended for use only by the addressee. The views and opinions expressed in this email are the senders own and do not represent the views and opinions of ACT Financial Systems (Asia Pacific). --=====================_3981645==_.ALT--