Reorganizing the top level structure of branches in the svn repository.

Motivation Proposal Backwards Compatability Feedback Voting Links

Justin Deoliveira

1.7.x, trunk

Completed.

There are currently a couple of issues with the structure of our svn repository.

The first issue is that some of the directory names are misleading. Examine the current structure:

  geoserver/
     configuration/
     geoserver/

The configuration directory is the directory that contains all the well-known geoserver data directory configurations. The issues with this is that those directories do not contain just configuration, but data as well. A name that reflects this would be an improvement.

The geoserver directory is the root of the source tree. It should be renamed to something that reflects that it contains source code.

The title days it all. A place to store documentation that is versioned is needed.

The rationale behind “geoserver_data” is twofold. It lets the person know that this directory contains actual data, and better mirrors the fact that it is the root of the “data” directory tree.

The name “source” is more indicative of the root of the source tree than the name “geoserver”.

A tree is needed for documentation, namely the user guide and the developer guide. Creating a directory named “documentation” with two subdirectories named “user” and “developer”.

geoserver/
   data/
      release/
      citewfs-1.0/
      ...
   doc/
      developer/
      user/
   src/
      main/
      platform/
      ows/
      ...

Not applicable.

Andrea Aime: +1 Alessio Fabiani: Justin Deoliveira: +1 Jody Garnett: Saul Farber: Rob Atkinson:

JIRA Task Email Discussion Wiki Page