It would save much time for deployment of web-applications during development, if the jar-files of cocoon can be placed in the classpath in another place than WEB-INF/lib
For example, JBoss has the ability to put jar files in server/default/lib; These jar-files are attached in the classpath of web-apps. Will Cocoon work when all cocoon jars are placed in server/default/lib instead of in WEB-INF/lib? The Cocoon.war webapp will be much smaller and thus deploy much faster. Regards, Kees > I am at a stage where I will need to deploy some applications under > Cocoon. It would be nice to be able to bundle up the applications into > wars. The war would contain the application sitemap, required jars, > xslt, images, etc. Then copy the war under cocoon and have cocoon expand > the war. Is this possible?. > > Also how do you get around the requirement for application A and > application B requiring different versions of a jar, say foo1.jar and > foo2.jar ?. At the moment I copy the jars into the WEB-INF/lib dir under > cocoon, but this means that all applications can see that jar. > > > Nick Frangos > > -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 24 November 2004 7:25 AM > To: [EMAIL PROTECTED] > Subject: RE: Deployment of Cocoon apps. Best practices? > > I also use maven. These are the steps I follow: > 1. Build Cocoon with only the desired properties and blocks. Use > ./build.sh war > 2. Copy the generated war file to the maven repository. > 3. In the project directory run maven war:install using the attached > maven.xml in the project directory. It unwars the cocoon war, patches > the sitemap and cocoon.xconf as necessary and then adds our stuff to the > war. > > Note that this means that the vast majority of the jars you will be > using will be brought in via the cocoon war file, dramatically reducing > the number of dependencies that have to be changed with each cocoon > update. > > Ralph > > > Eric Jacob said: >> Hi Andr�, >> >> I'm successfully using Maven to build and deploy my Cocoon projects. >> >> Here how I manage it: >> >> - Rename blocks.properties and build.properties to >> local.blocks.properties and local.build.properties; >> - Uncomment all unused stuff; >> - Build Cocoon; >> - Copy all the generated jars to your local Maven repository (in my >> case, I >> use maven-proxy); >> - Copy the webapp folder (in build/webapp) to my Maven working dir >> (src/webapp), except the jars. >> - Create a project descriptor extending cocoon-2.1.6.xml. >> >> I've put in attachment a Maven project descriptor for building a >> minimal Cocoon webapp. Here my directory structure: >> >> -root/ >> |-cocoon-2.1.6.xml >> |-projectA/ >> |-src/ >> |-conf/ >> |-java/ >> |-test/ >> |-webapp/ >> |-... >> >> Hope this help. >> >> Eric > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
