Hi,
I'd like to propose a little modifications to the web-app module
that should help when building a customized version of GeoServer.
The current web-app module, as I see it, has the following issues:
- for some reason during the deploy of releases the jar ends up
containing other jars. E.g. see
http://repo.opengeo.org/org/geoserver/web/web-app/2.1.2/web-app-2.1.2.jar
This is actually the .war file with a different name.
This makes it hard to make a custom build on top of a release, which is
annoying since most people interested in custom build do want to
base it on a release.
- the web-app contains some crucial classes (filters), so it's needed,
but at the same time make choices about the dependencies that
might be unsuitable for custom builds. E.g., in some custom build
we might decide that we only need wms and wfs, and only support
for vector data, plus some assorted extras
I know, one could use maven exclusion mechanism, but it's imho
cleaner to add what is needed instead of listing what to remove
(might be a matter of preference)
What I would like is not having to depend on web-app to start with.
A custom build often has to roll its own web.xml anyways, so I believe
the best way forward would just to move the classes implementing
the filters back in main and have web-app be just the wiring that
builds a .war, and nothing else.
Given that all the pieces in GeoServer are made to build a web app
moving back the filters in main should not cause any trouble (besides
being trivial).
Opinions?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------