Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 17569 invoked from network); 7 Apr 2004 13:01:03 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Apr 2004 13:01:03 -0000 Received: (qmail 24889 invoked by uid 500); 7 Apr 2004 13:00:49 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 24811 invoked by uid 500); 7 Apr 2004 13:00:48 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 24722 invoked from network); 7 Apr 2004 13:00:47 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 7 Apr 2004 13:00:47 -0000 Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BBCfg-0001jw-00 for ; Wed, 07 Apr 2004 15:00:48 +0200 Received: from giraffe.student.utwente.nl ([130.89.169.128]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2004 15:00:47 +0200 Received: from lsimons by giraffe.student.utwente.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2004 15:00:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@cocoon.apache.org From: Leo Simons Subject: Re: [Kernel22] How to develop a component? Date: Wed, 07 Apr 2004 13:55:56 +0200 Lines: 48 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: giraffe.student.utwente.nl User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 X-Accept-Language: en-us, en In-Reply-To: Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi guys! Nicola Ken Barozzi wrote: >> And the dependency is very minimal. It's just a dependency against the >> avalon framework api version 4.1.5 - a released version. There is no >> need in following the development of Avalon. > > The issue is not so technical as it's of indipendence from something > that, in the good and the bad, has not helped Cocoon be built by Gump > for ages now. avalon-framework very rarely doesn't get built by gump. It's the ECM dependency that's causing the ripples, and the big set of dependencies ECM has itself. Since it seems ECM is being put into the freezer anyway, just be pragmatic and make the gump build of cocoon depend on an installed package or some jars in cvs. It's not like ECM has changed a lot over the last 2 years. (...) I just read up on this thread when someone pointed me at it. What I don't understand is what you think will be so difficult. By now there's half a dozen examples of containers and/or microkernels out there that can be easily made to run your typical avalon-style cocoon component. Just to drive that point home, here's some tests from my own pet project: http://cvs.sourceforge.net/viewcvs.py/jicarilla/jicarilla-sandbox/platform/container-integration/src/test/org/jicarilla/container/test/integration/avalon/ if I can figure out how to do this all on my own, surely the cocoon community will have no trouble whatsoever attaining interoperability between "new-style" and "old-style" blocks you need. -- cheers, - Leo Simons ----------------------------------------------------------------------- Weblog -- http://leosimons.com/ Component Community -- http://componentplanet.org/ Component Glue -- http://jicarilla.org/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett