Index: changes.xml =================================================================== RCS file: /home/cvspublic/jakarta-jetspeed/src/plugins-build/jetspeed/xdocs/changes.xml,v retrieving revision 1.1 diff -u -r1.1 changes.xml --- changes.xml 11 Feb 2003 23:34:56 -0000 1.1 +++ changes.xml 28 May 2003 21:02:05 -0000 @@ -1,16 +1,16 @@ - - - Changes - Eric Pugh + + + Changes + Eric Pugh - - - - Initial cut of plugin - - - + Updated documentation on goals + + + Initial cut of plugin + + + Index: goals.xml =================================================================== RCS file: /home/cvspublic/jakarta-jetspeed/src/plugins-build/jetspeed/xdocs/goals.xml,v retrieving revision 1.1 diff -u -r1.1 goals.xml --- goals.xml 11 Feb 2003 23:34:56 -0000 1.1 +++ goals.xml 28 May 2003 21:02:05 -0000 @@ -1,21 +1,18 @@ - - - - Maven Jetspeed Plug-in Goals - Eric Pugh + + + Maven Jetspeed Plug-in Goals + Eric Pugh - - - - jetspeed:war-cactus - - Take a vanilla Jetspeed war and expand it into a working directory. Then war up the project, - expand it into the working directory, and merge in the properties. Then rewar everything and - place the new war in the orignal war location, but with all the new stuff. - - - + + + + jetspeed:overlay + This gaol should be used when you want to take your code, overlay over a plain vanilla jetspeed war file, and then run cactus tests against the resulting codebase. That way your cactus tests do not have to deal with what the current state of the production jetspeed version.

+ The goal takes a vanilla Jetspeed war specified in the project.properties as maven.jetspeed.vanilla.war=C:/portal/src/jetspeed-upstate/portal2.war and expands it into a working directory. Then the project is turned into a WAR file, and expanded over the vanilla \ installation in the working directory. Lastly, the properties files are merged in. The resulting overlayed codebase is then re WAR'ed, and the plugin places the new war in the orignal war location, but with all the overlayed code and merged properties.

This is useful when running cactus tests, as you can just run: maven war:webapp jetspeed:overlay cactus:test + + + jetspeed:merge-properties

This goal is called by jetspeed:overlay to merge in specific properties files into the base vanilla jetspeed installation. Currently this is pretty rigidly definied which files are merged.

The plugin expects the files to be in ${maven.jetspeed.merge.dir}/MergeJetspeedResources.properties, and typically the maven.jetspeed.merge.dir is in the ./src/conf directory of your webapp. The files that are currently merged are:

  1. MergeJetspeedResources.properties
  2. MergeJetspeedSecurity.properties
  3. MergeTurbineResources.properties
  4. MergeTorque.properties
These are merged into the corresponding default versions (without the word Merge ;-) ).

Index: index.xml =================================================================== RCS file: /home/cvspublic/jakarta-jetspeed/src/plugins-build/jetspeed/xdocs/index.xml,v retrieving revision 1.1 diff -u -r1.1 index.xml --- index.xml 11 Feb 2003 23:34:56 -0000 1.1 +++ index.xml 28 May 2003 21:02:05 -0000 @@ -2,14 +2,14 @@ - Maven Castor Plug-in - Jason van Zyl + Maven Jetspeed Plugin + Eric Pugh -
+

- A plugin that currently just sets up castor for use in Jelly + A plugin that currently can build a Jetspeed War File, or take an existing WAR file plus custom code and product a merged Jetspeed WAR file ready for Cactus testing.

Index: properties.xml =================================================================== RCS file: /home/cvspublic/jakarta-jetspeed/src/plugins-build/jetspeed/xdocs/properties.xml,v retrieving revision 1.1 diff -u -r1.1 properties.xml --- properties.xml 11 Feb 2003 23:34:56 -0000 1.1 +++ properties.xml 28 May 2003 21:02:05 -0000 @@ -7,18 +7,18 @@ -
- - - - - - - - - - - +
+
Property nameOptional?Description
+ + + + + + + + +
Property nameOptional?Description
maven.jetspeed.vanilla.waryesLocation of the jetspeed.war file. By default ${plugin.dir}/jetspeed.war
maven.jetspeed.merge.dir yes Where to look for the Merge* files. By default ./src/conf/