Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 93412 invoked from network); 3 Dec 2001 15:16:04 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Dec 2001 15:16:04 -0000 Received: (qmail 23286 invoked by uid 97); 3 Dec 2001 15:16:03 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 23270 invoked by uid 97); 3 Dec 2001 15:16: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 23259 invoked from network); 3 Dec 2001 15:16:02 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: removing deprecated stuff References: From: Stefan Bodewig Date: 03 Dec 2001 16:09:27 +0100 In-Reply-To: "Sam Ruby"'s message of "Mon, 3 Dec 2001 10:02:44 -0500" Message-ID: Lines: 28 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.4 (Civil Service) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 3 Dec 2001, Sam Ruby wrote: > Stefan Bodewig wrote: >> >> (not Ant itself as an older >> version of Ant won't have the -legacy switch, obviously) > > Just curious, what's "obvious" about that statement? Ant 1.4.1 won't be magically replaced with a version that contains a backported -legacy switch. > To date, it appears that the working assumption is that developers > will bootstrap when necessary. "Ant" developers are expected to bootstrap Ant if necessary, same for people who want to build their "released" Ant version from sources. > By the way, I am *very* concerned that -legacy will be used too > aggressively. IMHO, it should only be used after a *significant* > period of deprecation, containing at a minimum one public release. At least I have never said something different. When I proposed it (actually have been thinking loud, as I didn't really propose it), I talked about affecting all stuff that has been deprecated in Ant 1.4 - which would be two releases ago when Ant 1.5 appears. Stefan -- To unsubscribe, e-mail: For additional commands, e-mail: