> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of > Ovidiu Predescu > > On Thu, 11 Apr 2002 17:36:34 -0400, "Vadim Gritsenko" > <[EMAIL PROTECTED]> wrote: > > > > All the non-essential core components and the functionality which > > > builds on top of the core should appear in different directories. > > > > > > For example, we'd have hsql/, crawler/, deli/, hsqldb/ and so on, > > > appear as sibling directories of the core/ directory. Each of these > > > directories contains the code, documentation, tests, build file, > > > everything they need. > > > > > > > Ovidiu, > > > > How this will speed up "build webapp"? You lost me... > > It will not help "build webapp", but the build for the functionality > you work on. > > Most of the time, your work focuses on a very small part of > Cocoon. Building only that part only will speed up the process > dramatically. You don't need to recreate a huge jar file just because > a single Java class has been modified. You recreate only a smaller jar > file, containing that class, and copy it over in the common build > area, where all the other jar files are located. > > Does it make sense?
You can achieve this without restructuring repository: 1. Set up build.xml to create several smaller jars, or 2. Setup target to do WEB-INF/classes deployment instead of cocoon.jar (almost like webapp-local target, but without creating jar file) Vadim > Ovidiu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
