From commons-dev-return-184-apmail-xml-commons-dev-archive=xml.apache.org@xml.apache.org Mon Nov 18 08:46:54 2002 Return-Path: Delivered-To: apmail-xml-commons-dev-archive@xml.apache.org Received: (qmail 87794 invoked by uid 500); 18 Nov 2002 08:46:54 -0000 Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list commons-dev@xml.apache.org Received: (qmail 87784 invoked from network); 18 Nov 2002 08:46:53 -0000 Received: from bodewig.bost.de (195.227.98.11) by daedalus.apache.org with SMTP; 18 Nov 2002 08:46:53 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.11.6/8.11.6) id gAI8l3o22650; Mon, 18 Nov 2002 09:47:03 +0100 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org CC: commons-dev@xml.apache.org Subject: Re: Need help with backwards incompatible resolver change References: <3DD54298.6030507@arielpartners.com> From: Stefan Bodewig Date: 18 Nov 2002 09:47:02 +0100 In-Reply-To: Message-ID: Lines: 19 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 18 Nov 2002, Stefan Bodewig wrote: > I'll see whether I can put together a patch to resolver today - if I > can't I'll tell you why 8-) Well, I certainly cannot re-introduce a static setIgnoreMissingProperties method to CatalogManager as there now already is a non-static method by that name. I don't see an easy solution for this apart from renaming the instance methods. The same is true for the Debug case. Ant could switch to the 1.1 resolver code as the Ant release that uses resolver is still a couple of months away - after a release of resolver 1.1, I guess. But you better start thinking about a proper deprecation policy 8-) Stefan