Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 34748 invoked by uid 500); 31 Jul 2002 15:23:28 -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 34734 invoked from network); 31 Jul 2002 15:23:28 -0000 Message-ID: <3D480261.6020905@wkwyw.net> Date: Wed, 31 Jul 2002 16:29:37 +0100 From: Ross Gardler User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901 X-Accept-Language: en-us MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [Proposal] Cocoon Organization References: <002001c23895$ff7a6890$ac00a8c0@Gabriel> <3D47ED8E.3090903@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Gianugo Rabellino wrote: > Berin Loritsch wrote: > >> We should split Cocoon into core development and component development >> efforts, much like Avalon does with Framework and Excalibur. That will >> allow the components to be packaged in jars that serve a similar >> purpose. > > > Yes, +1, go for it, hippy-ya-ye-o! This is badly needed. How does this relate to the Cocoon Blocks idea? (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=102528398016325&w=2 for start of thread). It strikes me that there is a certain amount of overlap between these two activities. Ross --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org