Hunting through email to see what was needed to complete this work, email "gt-process planning" from Jul 3 2011 had a few tasks most of which were actually done (making annotation based base classes etc...).
5) Moving the good bits into the library - the actual interfaces can move to gt-api - the core implementations to gt-main (my preference) or gt-metadata depending on if they are useful for raster processing? - this would leave plugins/process as an optional plugin that contains only basic "literal" processes A lot of this actually happened, except for the bit about moving the core interfaces and implementation into the core library. The actual API seems solid (ProcessExecutor, Process, Processors, ProcessFactory). Q: Would it be sensible to move these into gt-main making process a 1st class idea alongside function? Q: There are two annotation based base classes for process implementation; I expect we need only one... any preference? -- Jody Garnett
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
