Hi,
these days I've tried to setup a single eclipse workspace where
all the geoserver projects do depend directly on the needed geotools
projects. This would speed up development, because one could simply
work directly in Eclipse, without having to build and refresh the
modified gt2 modules in order to make the geoserver ones see them
(which is what you get when you run mvn eclipse:eclipse separately
on the two modules).
Well, in theory the recipe is simple:
*) checkout the two projects side by side
*) create a fictitious super-pom that has geoserver and geotools
as modules
*) run mvn eclipse:eclipse from that root
In practice, this does not work. First I had to upgrade commons
logging, otherwise GeoServer run from the "Start" java program
would crash during startup (due to silly dependencies the old
commons logging had).
After fixing that, GeoServer starts, but other issues are waiting.
Test running from Eclipse start to fail (and they would not from
maven, or using the old separate mvn eclipse:eclipse approach).
Little investigation shows the problem lies in some gt2 modules
still using epsg-wkt for tests. This ends up in the eclipse
project classpath, and transitively up to the geoserver
unit tests and Start program. This means both epsg-wkt and
epsg-hsql are in the classpath, and hell doors open.
To solve that all projects still using epsg-wkt for testing
would have to be upgraded to epsg-hsql... but I'm a little
discouraged, this "time saving" thing is ending up being quite
a time sink instead. What awaits me when the epsg-xxxx issue
is fixed?
Did anyone successfully managed to have everything working?
If not, at least you know what the problem is, and you won't
have to go thru the same debugging as me to find out why.
Cheers
Andrea