Justin Deoliveira a écrit :
> Doing the 2.5.0 release i ran into a minor issue with the newly added
> imagemosaic-jdbc module. It depends on gt-coverageio which is
> unsupported. So to include it in the release we would have to include
> coverageio... which goes against our plan of excluding unsupported modules.
The issue depends on which part of coverageio is used exactly:
* If this is "image metadata", then this part may change. It requires
agreement between different ImageReader potential implementors.
* If this is "image mosaic", then this part is expected stable now.
* If this is the abstract "GeographicImageReader" base class, then
I do not expect change in this class neither.
Possible approachs:
* Graduate parts of the "coverageio" module, exclusing among others the
"Image I/O metadata" part. I think that it would be premature to graduate
the whole coverageio in public API, but we may graduate selected parts of
it depending on user need.
or
* Apply a small amendment to our policy. Instead of saying "stable module
can not depends on unsupported module", we could said "this module
(gt-coverageio) is not public - it does not appear in the javadoc and
users should not be aware of it, unless they can afford changes in the
API. However whatever a supported module use it or not is implementation
details that users don't need to know."
Martin
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
