On Fri, Aug 16, 2002 at 11:23:44AM +0200, Carsten Ziegeler wrote: > Some time ago, the excalibur project has split up their distribution > of components into several subprojects. We use some of them (for > example the component, xmlutil, store subproject etc.). > > Each of these subprojects creates its own library - the full > avalon-excalibur.jar > is only there for compatibility. > > I would suggest that we skip to all these nice little jars > and remove the big avalon-excalibur.jar. > > The advantages: > - We only include those subprojects we need > - We minimize the build problems with excalibur > - Updating for example to a new store implementation, requires only > updating this subproject and not everything > - The JDK depency is limited to one small jar, the datasource subproject > which is optional for Cocoon, so the Cocoon core is no longer JDK > dependend > - If a bug is in one excalibur subproject we only have to revert this > subproject and not all. > > Disadvante: > - More smaller jars instead of one big one. > > Here is my +1
This absolutely makes sense to me! Why do we need update the whole of excalibur (with all the potential problems that could cause) just to update one partuclar component! Here is my vote (if it counts for anything :-P) +1 Regards, Michael Melhem > > Carsten > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
