I'd thought about the plugin idea for managing the build, as I've a maven script thats pretty much ready to be ported out into a plugin.
Reinhard what's your view on this as you seem to have a different vision? How possible is it to have installable blocks? For example I've had a few problems using a forms block built with 2.1.7-dev, with 2.1.6.
see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=110914428922649&w=2 and http://svn.apache.org/repos/asf/cocoon/whiteboard/block-deployer/
Looking at it there doesn't seem to be a huge reason why the blocks couldn't be installable, i guess compatability testing against release versions would be needed. But I cant get passed thinking that its all supposed to be java.
I might not know what I'm talking about but I don't see the comparision between httpd server and a framework as the same thing. The users are different as well as the technologies.
Folks developing java webapps, expect to have jar files they need to stick in WEB-INF/lib deploy to a container such as tomcat and run the thing.
When I'm doing sys admin stuff i like using vi, running configure scripts and makefiles. But i wouldn't code java using vi.
I've been going through the svn logs. Are there's any posts in the archieves where I can brush up on what the road map is?
read http://wiki.apache.org/cocoon/Blocks to catch up what's our vision on blocks is.
--
Reinhard P�tz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
