GeoServer : GSIP 6 - Track GeoTools Trunk
This page last changed on Jan 23, 2007 by cholmes.
Move GeoServer trunk to geotools trunk
Voting, even with acceptance no work will commence until GeoTools policy is changed as described below.
Other wiki discussions:
GeoServer development is driving the majority of changes in the GeoTools library (ie trunk), and GeoServer does not maintain a build tracking GeoTools trunk leaving us open to surprises when it comes time to update; it also leaves GeoTools trunk unstable with respect to our needs.
We can be involved and control the GeoTools development cycle; the stratagy hinges on GeoTools being made available in a timely fashion.
The following assurances have been requested from the geoserver team with respect to this assumption:
We should make a build tracking GeoTools trunk - for clarity this should be GeoServer trunk.
Update the maven2 dependencies on GeoServer trunk to point towards 2.4-SNAPSHOT.
GeoTools 2.4 is unstable; currently this is due to activity on the OWS4 geoserver branch and work needed for the future of our WCS support. Since these RnD efforts are both GeoServer based the developers involved are already in communication with the project.
A more serious risk is that GeoTools is not suitable for our future needs (see link above); we will need to take part in the planning process and ensure our requirements are met in a timely fashion.
There is a risk that other applications (such as uDig will drive changes adverse to the geoserver roadmap). Channels of communication must remain open.
|Document generated by Confluence on May 14, 2014 23:00|