Overal directory structure

This is applicable starting from version 1.5.0. Previous versions do not support the module based structure!

The Geomajas directory structure has been created with the generic module conventions in mind:

- geomajas
-- geomajas-api : interfaces which serve as public API for Geomajas.
-- geomajas-impl : implementation of the public API
-- geomajas-dojo-server : server side aspects of the dojo client face.
-- geomajas-dojo-client : client side module when using the dojo face.
-- geomajas-gwt-server : server side aspects of the gwt client face.
-- geomajas-gwt-client : client side module when using the gwt face.
-- layermodels
--- geomajas-layermodel-geotools
--- geomajas-layermodel-hibernate
--- geomajas-layermodel-wms
--- geomajas-layermodel-google
--- geomajas-layermodel-openstreetmaps
-- extensions
--- geomajas-printing
--- geomajas-editing
- geomajas-dojo-example : full example using dojo, similar to majas-tutorial in 1.4
- geomajas-dojo-simple : simple example project
- geomajas-gwt-example : full example using gwt, similar to majas-tutorial in 1.4
- geomajas-gwt-simple : simple example project
- pom.xml : very thin pom, only declares the five main projects, nothing more

Applications should only depend on the api, dojo-client and gwt-client modules for programming against. Dependencies on layermodels/extensions (individual or grouped) will be needed for deployment to pull in the needed bits.