cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <ovi...@cup.hp.com>
Subject Re: [PROPOSAL] splitting Cocoon
Date Wed, 10 Apr 2002 21:44:38 GMT
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:
> 
> Index: build.xml
> ===================================================================
> RCS file: /home/cvspublic/xml-cocoon2/build.xml,v
> retrieving revision 1.197
> diff -u -r1.197 build.xml
> --- build.xml	10 Apr 2002 06:57:27 -0000	1.197
> +++ build.xml	10 Apr 2002 21:24:15 -0000
> @@ -1206,8 +1210,11 @@
>      <taskdef name="manifest-tool" classname="ManifestToolTask" 
>          classpath="${tools.dir}/anttasks"/>
>  
> -    <manifest-tool directory="${build.war}/WEB-INF/lib"
> manifest="${build.war}/WEB-INF/Manifest.mf"/>
> +    <manifest-tool directory="${build.war}/WEB-INF/lib"
> +                   manifest="${build.war}/WEB-INF/Manifest.mf"/>
> +<!--
>      <jar jarfile="${build.dir}/${name}.war" basedir="${build.war}"
> includes="**" manifest="${build.war}/WEB-INF/Manifest.mf"/>
> +-->
>    </target>
>  
>    <!--
> =================================================================== -->
> 
> 
> 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.

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.

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