cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <>
Subject [Proposal] Cocoon Organization
Date Wed, 31 Jul 2002 13:27:19 GMT
Currently Cocoon is 1.5 MB in size.  That is a huge jar.  In Cocoon
are the core files, the servlet compatibility files, the CLI
files, and hundreds of components.

The fact that we as a community are thriving is excellent.  However, as
project, Cocoon is feeling quite heavy.  Esp. since there are features
Cocoon that not everyone needs.  I proposed this a while back, but I am
going to propose it again.

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
Things like all the database related components should be in their own
mini-project.  Each mini-project has its own documentation, and its own
life.  It also allows each mini-project to determine whether it is ready
for prime-time or not.  At every release, the core cocoon does not have
to worry about which components it has to move into scratchpad.  Also
each set of components has a little focused mini-community so the docs
get upgraded in a focused manner.

I have already seen the benefits of how this works in Excalibur--now
we are going through systematically.

When I am generating a site, I don't want to have to include the portal
components or the DB and auth components.  Those don't need to be there
for the site.

Keep in mind that the mini-projects are all part of the cocoon umbrella,
and they foster functioning communities within the larger Cocoon
not detract from it.

"They that give up essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."
                - Benjamin Franklin

To unsubscribe, e-mail:
For additional commands, email:

View raw message