[Geoserver-devel] community module handling

Hi all,

There are some issues with how community modules are handled by our build:

* community profile includes everything

This leads to people hacking the pom and commenting out particular
modules, only including the one they need

* web module dependencies

To get a community picked up at runtime the web pom.xml must be hacked
and it has to be added as a dependency

So... I have made the following tweaks:

* Created profiles for each community module

This allows us to specify community modules individually, like:

mvn -P geosync,geosearch clean install

* Added same profiles to web.xml

The same profiles also add the dependency in the web modules pom.xml.

Currently i have added the following profiles:

* geosync
* geosearch
* rest

As they are the only modules that seem to be active currently. If i have
missed any please tell me or update the pom and add the profile.

-Justin

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Justin Deoliveira ha scritto:

Hi all,

There are some issues with how community modules are handled by our build:

* community profile includes everything

This leads to people hacking the pom and commenting out particular
modules, only including the one they need

* web module dependencies

To get a community picked up at runtime the web pom.xml must be hacked
and it has to be added as a dependency

So... I have made the following tweaks:

* Created profiles for each community module

This allows us to specify community modules individually, like:

mvn -P geosync,geosearch clean install

* Added same profiles to web.xml

The same profiles also add the dependency in the web modules pom.xml.

This looks like a good idea indeed.
Cheers
Andrea