+1 Carsten
> -----Original Message----- > From: Per-Olof Norén [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 12, 2001 5:13 PM > To: [EMAIL PROTECTED] > Subject: Re: Make available a cocoon2-blank.war please! > > > > ----- Original Message ----- > From: "giacomo" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "Matteo Di Giovinazzo" <[EMAIL PROTECTED]> > Sent: Sunday, November 11, 2001 11:48 AM > Subject: Re: Make available a cocoon2-blank.war please! > > > > On Sat, 10 Nov 2001, Ovidiu Predescu wrote: > > > > > On Sun, 11 Nov 2001 03:13:22 +0100, "Matteo Di Giovinazzo" > <[EMAIL PROTECTED]> 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! > > > > > > > > See on Jakarta Struts: the struts-blank.war contains all > that's needed > for > > > > running the webapp! > > > > > > Rather than a WAR file I think we need a .tar.gz and .zip which > > > contains a whole directory structure, that people can take and start > > > adding their own things to build their Cocoon-based Web > > > application. It should contain a configurable build.xml which compiles > > > the application, and builds the WAR file of the application. > > > > > > I have such a directory structure setup here at HP as an easy way to > > > jump-start Cocoon-based projects. The directory structure is like > > > this: > > > > > > your-webapp/ > > > bin/ > > > ant > > > ant.bat > > > antRun > > > antRun.bat > > > lcp.bat > > > lib/ > > > avalon-excalibur-4.0.jar > > > avalon-framework-4.0.jar > > > batik-libs.jar > > > cocoon.jar > > > dom2.jar > > > hsqldb.jar > > > jakarta-regexp.jar > > > javac.jar > > > logkit.jar > > > maybeupload.jar > > > resolver.jar > > > xalan.jar > > > xerces.jar > > > src/ > > > webapp/ > > > WEB-INF/ > > > logkit.xconf > > > web.xml.in > > > cocoon.xconf > > > sitemap.xmap > > > build.bat > > > build.sh > > > build.xml > > > > > > The build.xml builds the Web app in a build/ directory, and could be > > > configured to copy only the jar files needed by your application. > > > > > > I can add this to the repository and update Cocoon's main build.xml to > > > create a separate .tar.gz/.zip distribution for this if we agree on > > > it. What would be a good name for a subdirectory inside Cocoon that > > > contains this? > > > > Sounds like a CDK. It also touches the discussed RT about CAR (Cocoon > > webapp archive) to enable deployment of individual apps into one Cocoon > > instance. > > > > I suggest to have a ant target to build it. The place to have the needed > > files for it (special build.xml, sitemap.xmap, etc) should go into the > > src/cdk directory (once we have moved to a Avalon like structure of the > > repository). > > > > What are others think about it? > > I Look at it as a "least-common-denominator" build target containing only > the bare minimum > of contents in the xconf and sitemap files. It should be a build target > +1 from sweden :-) > > /Per-Olof Norén > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
