cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: CoWarp (was Re: svn commit: r232855...)
Date Tue, 16 Aug 2005 09:27:57 GMT
Sylvain Wallez schrieb:
> Carsten Ziegeler wrote:
>>For the demo portal, I replaced the authentication framework with CoWarp
>>which provides imho a much nicer and cleaner way for plugging in your
>>authentication mechanism.
> CoWarp is a 35 kb jar file containing 25 classes which seem highly tied 
> to Cocoon and Avalon. Do you plan to move this code to the Cocoon repo?
> That would be IMHO a good thing to do to avoid the multiplication of 
> small jars and give a better community oversight on this interesting stuff.
If there is *high* community interest in hosting it at Apache I'm willing to
move. In fact, lack of a community was one of the main reasons in
creating Cowarp outside of Apache. Look at many of our blocks (incl. the
famous authentication block), most of them do not have a community.
They're a one man show (or sometimes a two man show). Apache is about
communities, and I think as long as the project does not have a real
community it should not be at Apache.
So, my suggestion is, if there are people interested in it, speak up,
lets create a comunity outside at Apache first and then move it.

And I think currently we have way too many blocks and adding another one
makes Cocoon even complexer. It seems everyone who has a good idea just
adds another block (with no or minimal community). Just adding a jar
dependency is much simpler from the complexity point of view.

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 :)

In the end, yes, I'm willing to move if this creates a community here.

Carsten Ziegeler - Open Source Group, S&N AG

View raw message