Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 77813 invoked by uid 500); 10 Feb 2003 15:57:03 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 77756 invoked from network); 10 Feb 2003 15:57:02 -0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 10 Feb 2003 15:57:00 +0000 Subject: Deprecation of the Avalon classes... From: Pier Fumagalli To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Folks... Avalon deprecated ComponentManager in favor of ServiceManager, but in the 2.1 codebase, although we import the new libraries, all the kit still relies on the Composable interface... It looks like that around 80/100 classes implement the deprecated stuff, should we go around and change those? Pier --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org