Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3


This proposal would like to refine how we are handling unsupported modules:

  • The creation of a single page in the developers guide outlining all the requirements from creation through supporting a module (right now this content is split across several pages). We should clarify how a module can drop back to unsupported status and so forth.
  • Modify the unsupported/pom.xml so that profiles are available grouping like functionality; using a single environmental -Dall to turn on all functions
  • Deployment of all modules to maven (including those in unsupported)
  • Continuous testing of all modules (including those in unsupported)
  • Restrict unsupported modules from the default download

The goals here are several fold:

  • Ensure that everything we (ie the PMC) make available for download has passed the Project QA checks and meets the requirements of our Developers Guide
  • Continue to foster new development
  • Ensure that GeoTools always builds in a reasonable amount of time


We would like to close up this issue in a timely fashion for the 2.5.0 release:



This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success


This proposal requires modification to the Developers Guide: