Apache Gump integration
Apache Gump builds Apache Forrest trunk and the latest development versions of each of our dependencies. This enables early detection of issues. Part of Gump's aim is to draw people beyond the project boundaries and assist with community integration and collaboration.
Because Forrest has many dependencies, we happen towards the end of the run. If dependencies (e.g. Apache Cocoon and certain blocks, Apache Xalan, etc.) fail, then of course the build of Forrest will fail.
The successful use of Forrest via Gump, indicates that we could update our supporting products to more recent versions.
ant, ant-contrib, xml-apis, xml-xerces, xalan, xml-resolver, xml-batik, xmlgraphics-commons, commons-cli, commons-collections, commons-jxpath, commons-io, commons-lang, commons-logging, concurrent, oro, logging-log4j-12, rat
The Gump metadata descriptor for Forrest defines a number of different projects. All ASF committers have access. Do 'svn co https://svn.apache.org/repos/asf/gump/metadata gump-metadata'
Via that metadata descriptor, Gump refers to targets named "gump-*" in our $FORREST_HOME/main/build.xml file.
See the Gump Object Model documentation.
Notifications are sent to the forrest-dev mailing list.
The top-level module for Forrest is at http://vmgump.apache.org/forrest/
The results at separate Gump installations (currently only one):
vmgump.a.o (Ubuntu Linux)
See notes about when Gump operates, what platform, and what JVM version.
This is the core of forrest.
This does 'forrest test-basic' to build our "seed-basic" site.
This does 'forrest gump-plugins' to deploy each of the plugins that is required by the 'forrest-test' gump project. The need for this step is explained at FOR-1235.
This does 'forrest test' to build our "seed-sample" site.
The ForrestBar tool.
Using Apache RAT (Release Audit Tool) to give some indication of the the state of our source code headers and some other license aspects.