Ralph Goers wrote:
My "wish" for Cocoon 2.2 has always been that
1. The "download" of Cocoon would be nothing more than installing a
maven plugin.
2. You'd use a Maven archetype to create a starter project. Ideally,
this is how the sample site should get created.
3. Building your project would automatically download the rest of cocoon
based upon the dependencies specified in the created project.
4. Building a project thus requires documentation on all the available
blocks, the services they provide, and how to invoke them.
Unfortunately, I am still almost entirely focused on Cocoon 2.1 so I'm
not certain how close we have gotten to my wish, but I have a feeling
that if we can't do this today the effort to get there is pretty minimal.
1-3 is already in place.
@4: There is already documentation available but it's not as complete as I would
like to see it :-(
What kind of documentation is missing most of all?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
