cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Separation of cocoon.jar into smaller pieces
Date Sun, 18 Jul 2004 15:02:26 GMT
Unico Hommes wrote:

> Reinhard Poetz wrote:
>> I also propose to separate the cocoon.jar into two parts: One that 
>> contains all interfaces that can be implemented and all classes that 
>> can be used or extended and a second jar that contains the rest which 
>> is only used internally. After migrating to Suversion this can be 
>> done without breaking the history because this will also require some 
>> file moving. IMO this step is necessary to separate our blocks from 
>> Cocoon core, isn't it?
> I like this too. There could be more than two parts though. There is 
> the API part that contains interfaces used to embed cocoon into a 
> certain environment. The SPI interfaces developers implement to extend 
> the functionality of Cocoon. The different API implementations that we 
> have (CLI, Servlet). And finally the core components.

Sounds fine. Any other thoughts?

As soon as we have migrated to Subversion I will prepare a proposal. 
What's the current status of the migration process?


View raw message