cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: HowToBuildAndDeployCocoonWithMaven
Date Tue, 30 Nov 2004 19:37:33 GMT
   Date: 2004-11-30T11:37:33
   Editor: EricJacob <eric.jacob@bell.ca>
   Wiki: Cocoon Wiki
   Page: HowToBuildAndDeployCocoonWithMaven
   URL: http://wiki.apache.org/cocoon/HowToBuildAndDeployCocoonWithMaven

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -28,7 +28,7 @@
  1. Move all the generated JARs (build/webapp/WEB-INF/lib) into your Maven repository;
  1. Copy the generated Cocoon webapp folder (build/webapp) to your project source directory
(e.g. projectA/src/webapp), except the JARs;
  1. Add the JARs dependencies to your Maven project;
- 1. Build Cocoon by typing ''build war'' or ''./build.sh war''. It will download the dependencies
into your local repository and create a WAR file.
+ 1. Build your project by typing ''build war'' or ''./build.sh war''. It will download the
dependencies into your local repository and create a WAR file.
 
 The drawback of this solution is the need to upgrade all the Cocoon blocks and dependencies
with each release (It could be a real pain, believe me!). Ralph's approach solves this problem.
 
@@ -39,7 +39,7 @@
  1. Copy the generated WAR (build/cocoon-2.1.6/cocoon.war) into your Maven repository (you
may want to rename it, for example cocoon-2.1.6.war);
  1. Add the WAR dependency to your Maven project descriptor;
  1. In maven.xml, add a preGoal element containing an unwar instruction for expending the
specified WAR;
- 1. Build Cocoon by typing ''build war'' or ''./build.sh war''. It will extract the Cocoon
WAR into your build directory, add your stuff and create another WAR file.
+ 1. Build your project by typing ''build war'' or ''./build.sh war''. It will extract the
Cocoon WAR into your build directory, add your stuff and create another WAR file.
 
 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.
 

Mime
View raw message