cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: Make available a cocoon2-blank.war please! [Chello 1.2]
Date Fri, 16 Nov 2001 15:19:43 GMT
On Thu, 15 Nov 2001, Ovidiu Predescu wrote:

> Hi Sebastien,
>
> On Thu, 15 Nov 2001 14:30:33 +0100, Sebastien Koechlin <skoechlin@ivision.fr> wrote:
>
> > > Is it possible make available a cocoon-blank.war webapp
> > > file for quickly starting up with a new web application
> > > that use Cocoon2?
> > > Also in the build.xml as a subtarget or a main target:
> > > it should be useful!
> >
> > I have just released chello 1.2 based on Cocoon2rc2
> >
> > This application is a minimal Cocoon 2 application.
> >
> > Chello is Open Source Software, released under the
> > IBM Public License and hosted on SourceForge
> >
> > Its main goal is to be a good start for any new Cocoon 2 project.
> >
> > The second goal is to help Cocoon developers to set up good practices
> > soon in their project : one line build command
> > (ant), unit testing (junit), functional testing, continuous integration,
> > documentation system...
> >
> > http://chello.sourceforge.net/
>
> This is great! It's exactly what I was thinking we need to have for
> Cocoon!
>
> One thing which might be good to have is the ability to customize the
> project name and the jar files which are copied into the webapp, based
> on customization properties in the build.xml file. For example
> javac.jar might not be needed if one uses jikes on the deployment
> machine. This would reduce the size of the deployed webapp
> substantially. Same for batik and other jar files.

I thought of an ant properties file where all components can be
specified to be included in a build of an cocoon2-blank.jar. These
components could be the Generators, Transformers, Serializers, Readers,
Matchers, Selector or Actions one would like to use for its project
(with their base jars needed as well[ie. SVGSerializers need
batik.jar]). Don't know exactly if such an approach can be used for the
general components as well (cocoon.xconf) and how those config files
(sitemap.xmap, cocoon.xconf and cocoon.roles) can be ajusted to these
selections and whether a skeleton sitemap can be generated according of
those settings.

My 0.02 euros to this.

Giacomo


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


Mime
View raw message