From: "Torsten Curdt" <[EMAIL PROTECTED]>
>
> <snip/>
>
> > 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
Not really a top necessity, but IMHO it's auspicable.
I'm +1 for a new module and +0 for a /optional dir in current cvs.
> b) a separation by package names
Yes, this was implied...
> 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.
Ant does it too.
But if someone doesn't feel safe if he doesn't do build clean compile...
;-P
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
