Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4301E470.4060103@apache.org>
Date: Tue, 16 Aug 2005 15:04:48 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: CoWarp (was Re: svn commit: r232855...)
References: <20050815185935.32798.qmail@minotaur.apache.org>
 <4300FE1D.2050606@dslextreme.com> <43018B96.9080904@apache.org>
 <4301AC67.8060001@apache.org> <4301B19D.90501@apache.org>
 <4301DCB5.1090402@apache.org>
In-Reply-To: <4301DCB5.1090402@apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:
> 
> It's not really here about adding a new block, but about providing a 
> simple and unified way of solving a common problem in Cocoon, which the 
> current pipeline-based auth-framework doesn't seem to solve (I 
> personally never used it).
> 
> The interfaces could be in core, along with the basic trivial 
> implementations, and blocks could provide specialized implementations 
> (e.g. JDBC, LDAP, JCR, etc).
> 
Ah, ok adding the classes to core makes imho more sense, agreed.

> 
>>Another advantage is that I can use Maven for building Cowarp -
>>something our build system does not provide. But for me using Maven is
>>another prerequisite :)
>> 
>>
> 
> 
> So let's switch Cocoon to Maven ;-)
> 
> Now why is it a prerequisite?
> 
:) Perhaps someone picks this up and finally moves Cocoon to use
Maven...(wishfull thinking)
Maven is soo simple for simple structured projects like cowarp. I get a
website and reports for free (incl junit tests - though cowarp currently
has none... :) ). And I don't want to miss this.


Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/