There is a procedure page on how to make your module supported. We are after: - a wiki page showing the status of your module - you have that - online tests - I am not sure if you have this or not? - test case coverage - hard to measure without online tests? - any user docs at all (see http://docs.codehaus.org/display/GEOTDOC/PostGIS+Plugin for example - the focus here is on a code example).
I thought that was all that was needed, Justin and Graham seem to be setting up a change proposal? Since the concept of a geometry plugin is new to GeoTools they need to make an API change (specifically a GeometryFactoryFinder). I do not think a change proposal is needed for the DB2 plugin - it does not introduce any new API. For the specifics please see this page: - http://docs.codehaus.org/display/GEOT/Supporting+your+module Cheers, Jody David Adler wrote: > What is needed to make this change, both procedurally and logistically? > > David > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
