Carsten Ziegeler wrote:
The more I think about it, I come to the conclusion that moving the blocks out of the core seems to be a good way to procede.What exactly does this mean? That the cocoon download does not contain any blocks?
(Moving files with SVN is easy and the history etc. is preserved).
(Of course we should only move things for 2.2 - 2.1.x should be left untouched)
Now one benefit of course is that our core gets smaller, but that's not really a reason to move things.
It's too early for this step. This requires a working distribution mechanism (see the BlockDeployer --> http://svn.apache.org/repos/asf/cocoon/whiteboard/block-deployer/)
If users have to now selectively download blocks in
addition to the cocoon core I think you'll just end up with a bunch of frustrated users. If, on the other hand, the core consisted of little more than what is needed to build the webapp and downloaded all the jars for the blocks then you'd have something.
I propose having a very small distribution (Cocoon core + core blocks which are IMO CocoonForms, Templating and JavaFlow) and a complete distribution with all blocks included.
--
Reinhard P�tz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
