Return-Path: 
 <ant-dev-return-20873-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 70263 invoked from network); 7 Dec 2001 02:02:59 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 7 Dec 2001 02:02:59 -0000
Received: (qmail 8423 invoked by uid 97); 7 Dec 2001 02:03:05 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 8374 invoked by uid 97); 7 Dec 2001 02:03:04 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 8352 invoked from network); 7 Dec 2001 02:03:03 -0000
Message-ID: <004601c17ec4$3d5a4360$c543d6d1@compaq>
Reply-To: "Magesh Umasankar" <umagesh@apache.org>
From: "Magesh Umasankar" <umagesh@apache.org>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
References: <NDBBIMHCHMPELMBMMFIMAEKCHFAA.conor@cortexebusiness.com.au>
 <3C0F7B58.42816D0C@i2.com>
Subject: Re: removing deprecated stuff
Date: Thu, 6 Dec 2001 21:09:43 -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 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

From: "Ken Wood" <kwood@i2.com>

> I agree with number 3. When I started getting deprecation warnings
> for my use of "rename", I was most pleased with the fact that
> the warning not only told me that rename was deprecated, but it
> also show what task and options to use to replace it. So I took
> a few minutes to edit my build.xml, and moved on with my life.

You said the answer yourself.  When you upgraded from say, Ant 1.2 to Ant
1.3,
you got this warning and you were most pleased.  Imagine a user upgrading
to Ant 1.5 from 1.1.  She wouldn't have got a single deprecation warning.
The mechanism of going about implementing Item 3 is what we are
addressing, I think. That is, the proposed mechanism would *recognize*
that Ant 1.5 no longer has <rename>, not work, and tell her that, instead of
acting as if <rename> is something new.  In other words, I think, removal of
deprecated stuff doesn't mean removal of *code* in most cases.  It just
means
making it unusable in a gracious way (by providing lots of How to Convert
type
messages).

And you know fully well why the legacy flag has been proposed... :-)

Cheers,
Magesh





--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>