Nicola Ken Barozzi wrote:...
This seems wrong, as blocks are to be hot-deployed by Cocoon, and this is instead an integral part of Cocoon that must be in the classpath before Cocoon starts.
For this, it was initially thought to use "modules", ie exactly the same thing that is now done with blocks, but that would not change later into real blocks.
Is it ok if I move it to a "modules" section and add the build of modules as for blocks?
I understand your concern. But what other "blocks" would be candidates for "modules"?
Any part in Cocoon code that is not necessary for using it as a bean and that needs extra library dependencies.
Can we foresee that Cocoon's core and the various environments can be modules too?
Exactly :-)
All environments have different jar dependencies, so moving them to modules we can, for example, compile Cocoon without servlet.jar, as the Servlet environment would be in it's own module.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------