I would say: yes, add the blocks directory. It would be good if the blocks
you add there are not already used in the cocoon-2.1 cvs, which means just
use unused names.
Given that any block follows a naming such as http://host/name/version, I would think that to avoid complications, we could represent that structure in CVS:
/src
/blocks
/cocoon.apache.org
/block_name
/jakarta.apache.org (???)
/block_name
/www.orixo.com (???)
/block_nameAnd versions are ignored as CVS already provides versioning.
Or would "our" block only be http://cocoon.apache.org/ even if we "wrap" stuff from other people? (I'm thinking about Jakarta Commons DBCP and POOL right now, maybe more stuff in the future)
Pier
Carsten
-----Original Message----- From: Pier Fumagalli [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 12:35 PM To: [EMAIL PROTECTED] Subject: Kernel...
The kernel is now all in CVS (it's still sucky, but I'm still working on it, at least now it compiles and - seems - to run nicely).
I have a few blocks that I want to develop around it (generic stuff, JDBC connection pool, poolable factories and event handling). I've noticed that in the Cocoon 2.2 tree there is no "/src/blocks" directory structure, can I put them in there?
Pier
smime.p7s
Description: S/MIME cryptographic signature
