On Fri, Mar 29, 2002 at 09:00:06AM -0500, Berin Loritsch wrote: > No, we change the master build script to build the same jar, > using the contents of all the other packages that were meant > to be in the main avalon-excalibur.jar file. (minus the > scratchpad stuff).
Okay, to confirm.. that means 'avalon-excalibur.jar' should contain: the old stuff in all/ cli collections concurrent i18n io naming instrument (the instrument dep was added recently) > The Excalibur-All jar is scary big (weighing in at a mere Meg) > > Keeping the original jars was (I thought) one of the things > we were doing. We were just adding the ability to grab the parts > of the jar you needed. And adding new parts. Hopefully, projects like Cocoon will eventually pick and choose components instead of relying on avalon-excalibur.jar. Cocoon doesn't need io, i18n, or concurrent, and could save 73k by not including them. --Jeff > > From: Jeff Turner [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > So I propose that we rename it to avalon-excalibur-core.jar > > (or something), to indicate that it's just the core subset classes. > > > > If we do that, then we might also consider renaming > > 'excalibur-all.jar' (built from the root build.xml) to > > 'avalon-excalibur.jar', since the 'all' is now redundant. > > > > > > --Jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
