cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: [PROPOSAL] splitting Cocoon
Date Wed, 10 Apr 2002 22:23:48 GMT
> From: ovidiu@orion.rgv.hp.com [mailto:ovidiu@orion.rgv.hp.com] On
Behalf Of
> Ovidiu Predescu
> 
> On Wed, 10 Apr 2002 17:27:40 -0400, "Vadim Gritsenko"
> <vadim.gritsenko@verizon.net> wrote:
> 
> > > From: ovidiu@orion.rgv.hp.com [mailto:ovidiu@orion.rgv.hp.com] On
> > Behalf Of
> > > Ovidiu Predescu
> > >
> > > Folks,
> > >
> > > During the development of Schecoon I really enjoyed the fast build
> > > time I would get compared to building Cocoon. On my machine doing
a
> > > "./build.sh -Dinclude.webapp.libs=true webapp" from scratch in
Cocoon
> > > takes 2 minutes and 10 seconds. In Schecoon a "./build.sh webapp"
> > > takes 25 seconds to complete.
> >
> > If you simply skip <jar/> step in the "webapp" target this alone
saves
> > lots of time. I have ./build/cocoon/webapp deployed in the tomcat
and
> > have a patched build.xml:
> >
...
> >
> > Why not just add intermediate target, something like "webapp-dir"?
> 
> Even with this trick, the time taken just to verify all the
> dependencies across all of Cocoon is too high.

At least something and can be done fast...


> Besides the point of having functionality grouped in a directory is
> that's easy to see what are all the files used to implement it. If
> they are put together in the same bucket is a lot harder to figure
> out.

Yup. Can't disagree.

Vadim


> Ovidiu
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message