well, 15MB is something :) It would be good, if I'd choose targets like FOP, ESQL etc. , then they'd be added to generated .war file incrementaly, together with all their dependent classes. So, I'll run "core", then I can run "add-fop", it goes into .war file with all its samples, sitemap samples etc. Like, Oracle's installator.
Otherwise, I don't see how are you going to componentize Cocoon, without manual resolving all dependencies. Argyn > -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 10:09 AM > To: [EMAIL PROTECTED] > Subject: RE: [Proposal] Cocoon Organization > > > > From: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] > > > > > -----Original Message----- > > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, July 31, 2002 9:27 AM > > > To: [EMAIL PROTECTED] > > > Subject: [Proposal] Cocoon Organization > > > > > > > > > Currently Cocoon is 1.5 MB in size. That is a huge jar. > > > > 1.5MB is nothing, unless you are going to implement Cocoon in PDAs. > > > Currently a full Cocoon with all support jars takes up over 15 MB. > Still thinking it's nothing? > > As we split the functionality out, things like Batik/FOP are in their > own separate component jar, along with their support jar. That means > that I don't have to have a 15 MB install if I don't want it. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
