cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [PROPOSAL] splitting Cocoon
Date Thu, 11 Apr 2002 14:36:38 GMT


> So we will have:
> cocoon-core.jar
> cocoon-optional.jar
> cocoon-scratchpad.jar
> In this way we have the advantage of fast compilation and clean dependency,
> without the need of havoc in the dir structure.
> So this spilt is core VS optional.
> When we will make the blocks, the core won't suffer.
> Does this make sense?

Indeed splitting cocoon into the core and the rest would be nice...
...but IMHO this makes only sense if we have

 a) different CVS repositories
 b) a separation by package names

Compilation time does not feel like a real argument to me. If you use a
nice IDE you can compile only the modified stuff until all errors are
fleshed out and then use ant to build the cocoon.jar. At least that's how
I do it...

To unsubscribe, e-mail:
For additional commands, email:

View raw message