Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
The following page has been changed by NiallPemberton: http://wiki.apache.org/struts/StrutsMaintenanceGump The comment on the change is: Notes on adding a packaged jar to gump ------------------------------------------------------------------------------ '''N.B.''' The gump '''metadata''' resides in SVN and '''can be updated by any committer''' - not just ''gump'' committers. ---- - - == Links == + == 1. Links == * [http://gump.apache.org/ Apache Gump Home] - for info on the gump concepts * [http://vmgump.apache.org/gump/public/ Latest Gump Run Info] * [http://vmgump.apache.org/gump/public/struts/ Latest Gump Run Info for Struts] - == Gump Metadata relevant to Struts in SVN == + == 2. Gump Metadata relevant to Struts in SVN == Gump metadata has been moved from CVS to SVN and now (Sept 2005) access to view the repository results in a '''403 Forbidden''' using either of the urls below: * http://cvs.apache.org/viewcvs/gump/ - as per the [http://gump.apache.org/ Gump Website] @@ -30, +29 @@ * project/struts.xml - '''Current Struts ''module'' using SVN''' * repository/struts-svn.xml - '''Struts SVN ''repository''''' - === profile/gump.xml === + === 2.1 profile/gump.xml === There are currently (as of October 6, 2004) two lines in the [http://cvs.apache.org/viewcvs.cgi/gump/profile/gump.xml gump.xml] ''profile'' which directly relate to struts: @@ -50, +49 @@ </profile> }}} - === repository/struts-svn.xml === + === 2.2 repository/struts-svn.xml === This file defines the Struts SVN ''repository'': {{{ @@ -60, +59 @@ </repository> }}} - === project/struts.xml === + === 2.3 project/struts.xml === This has been refactored since last time I looked and there are now four projects defined - for some reason there are two taglib ''projects'' - both seem to do the same thing !?! {{{ <module name="struts"> .... - .... <svn repository="struts-svn" dir="current"/> - .... .... <project name="struts-core"> ... </project> - <project name="struts-taglib-from-packages"> ... </project> - <project name="struts-taglib"> ... </project> - <project name="struts-tiles"> ... </project> - </module> }}} + == 3. Adding a Packaged Jar == + + Recently the addition of the maven-taglib-plugin to the taglib's '''project.xml''' caused gump to fail. I thought I would document the steps needed to add a '''packaged jar''' to gump to resolve this kind of issue. + + There are three steps to doing this (two which we can do and one which requires special kama) + + * '''3.1''' set up a project descriptor + * '''3.2''' add the project to the gump profile + * '''3.3''' upload the jar to the gump machine (''requires special kama for vmgump machine'') + + ==== 3.1 Project Definition ==== + Add an xml file definition to '''gumps metadata/project''' directory. The one for the maven-taglib-plugin is called '''maven-taglib-plugin.xml''' and looks like the following... + + {{{ + <module name="maven-taglib-plugin"> + <project name="maven-taglib-plugin"> + <jar name="maven-taglib-plugin-1.4.jar"/> + </project> + </module> + + }}} + + ==== 3.2 Update the Gump Profile ==== + + Add entries to the gump's profile by editing the '''metadata/profile/gump.xml''' file: + + * Add a '''module''' entry, for example... + + {{{ + <module href="project/maven-taglib-plugin.xml"/> + }}} + + * Add a '''package''' entry, for example... + + {{{ + <project name="maven-taglib-plugin" package="maven-taglib-plugin"/> + }}} + + ==== 3.3 Upload the jar ==== + The new dependency's jar needs to be uploaded to the '''vmgump''' machine. Someone with kama for the '''vmgump''' machine needs to do this - best way is to post a message to the [http://gump.apache.org/mail.html Gump Mailing List]. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
