Building

Building GeoServer Enterprise

Go to the source dir:

cd src

build using maven:

mvn clean install -Prelease

Perform a release

To perform a release you can use the Jenkins job configured here. Before start a geoserver release be sure to have a GeoTools Enterprise release, take a look here to understand how to proceed.

In order to start a run you have to setup the following parameters:

• BRANCH The branch to release from, “2.2.x” This must be a stable branch. Releases are not performed from master.
• REV The Git revision number to release from. eg, “24ae10fe662c....”, "HEAD". (Default is "HEAD")
• VERSION The version/name of the release to build, “2.2.5”, “2.3.6”, etc... (It will be used also as TAG)
• GT_VERSION The GeoTools version to include in the release. This may be specified as a version number such as “8.8-ENTERPRISE” or “2.7.5”.
• GWC_VERSION The GeoWebCache version to include in the release. This may be specified as a version number such as “1.3-RC3”.
• GIT_USER The Git username to use for the release.
• GIT_EMAIL The Git email to use for the release.
• PROFILES the profile to use during maven build (Default: charts,printing,control-flow,wps,xslt,querylayer,jp2k,gdal,oracle,sqlserver,arcsde,monitor,inspire,libjpeg-turbo,importer,cluster,activemq,release)
• DIST_PATH Local (to jenkins) directory where to copy artifacts (Default: /var/www/geoserver/downloads/releases/2.2.x/)
• DIST_URL Usually you don't need to change this, it represents the base url to show at the end of the job and may points to the deployed artifacts (Default: http://geoserver.geo-solutions.it/downloads/releases/2.2.x/)
• MAVEN_FLAGS Optional flags to append to the maven commands

NOTE:

If you need (for some reason) to perform again the same release you have to proceed as following:

1. Remove the tag from the repository git push origin :{TAG}
2. Login into jenkins
3. Clean the jenkins workspace from the gui using this link
4. Perform a new run as discussed above.