Well, I did a test - I upgraded my Geoserver to use Geotools 2.2. It
looks like there were no problems (I only had to trivially change one
line of a testcase).
I'm running CITE tests, and all looks good. Well, since we added the
ability to "plug-in" different output formats and advertise them in the
capabilities document, CITE has been complaining that our
GetCapabilities responses are not valid, even though they actually are.
Thats a real pain.... I'll probably add a
"stupid_CITE_conformance_hacks=1" to the config so that it doesnt
advertise its capabilities...
But, you can run geoserver with either geotools 2.1.x or 2.2 with no
problems.
AT THIS MOMENT - THERE'S LOTS OF COMMING CHANGING ON TRUNK SO THIS MAY
NOT BE TRUE OVER TIME.
** I dont think anything has really changed on trunk (other than
martin's stuff & he's been very good at keeping things compatible)
If you want to try this:
1. check out geotools 2.1.x and geotools trunk
2. "maven build" both
3. make sure your geoserver build.properties points to your maven
repository:
dir.maven=C:\\Documents and Settings\\Owner\\.maven\\repository
On my windows XP machine.
4. in build.xml around like 26 set "version.geotools" to either:
<property name="version.geotools" value="2.1.RC1" />
OR
<property name="version.geotools" value="2.2.x" />
5. Run the "geotools" ant directive (in build.xml)
* this copies all the geotools .jars from your maven repository to
your lib/ directory
6. build & deploy geoserver
Things should work normally. Some of the WMS changes are not on
geotools 2.2 (trunk) because we need to make a few decision as to what
the class is going to be called, etc...
dave
ps. just to repeat myself 3 times -- just because geoserver is, today,
compatible with 2.1.x and 2.2 (trunk) doesnt mean it will be in the
future.
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/