GeoServer : GSIP 11 - Data configuration handling
This page last changed on May 01, 2007 by cholmes.
Allowing developers to easily change data directory configurations without forcing people to download them.
Build system change
Targets are both Geoserver 1.6 and 1.5
Other wiki discussions:
Geoserver 1.4.x branch introduced the concept of configuration zip files, each containing a different and pre-configured data directory, some to be used for minimal configuration, other for releasing, other for CITE tests, and so on.
Installing one of these into the web module requires a plugin Justin developed, and setting an environemnt variable. For example:
in order to install the release configuration, which is to be found in the web module, release.zip file.
There are various downsides with the current situation:
We propose to have configuration kept in version control, in a place where people are not forced to download them, but easy for developers to handle and modify. Also each one will have to be a proper data directory, not a mix with service.xml and catalog.xml to be put in WEB-INF instead. Ideally, they can be used just fine by pointing GEOSERVER_DATA_DIR at them.
First step is to rework the geoserver svn layout so that there is a directory for code, and one for configuration.
This allows people that do not want to checkout the configurationts to get out just the code, whilst allowing developers to have all that's needed to run cite testing and releasing at their fingertips.
Second step is to modify the maven config plugin to copy the data directory from an arbitrary disk location, with two parameters:
The configurationsDir should be set by the developer as an environment variable once for all, allowing the mvn install to behave just like now.
In order to make the minimal configuration available to the developer that just checked out the code, we'll use the subversion external definition capabilities to link the minimal configuration directly under the web module. By default, we can have the config plugin look in the web module and the minimal configuration so that a mvn install just installs it.
|Document generated by Confluence on May 14, 2014 23:00|