I replied about the same topic on the GeoServer-devel. For visibility,
I'll mention things here as well...
Eclipse had approved hsqldb 2.3.0, so we happily used Maven to manage
our version, and we didn't encounter any problems with that.
The biggest hsqldb issue we had is that Hadoop also pulls in various
versions of hsqldb. One work-around would be for downstream projects to
shade hsqldb as they ship gt-epsg-hsql.
Cheers,
Jim
On 05/13/2015 03:45 PM, Jody Garnett wrote:
Taking this into a seperate discussion:
* hsqldb 2.2.8 -> 2.3
References:
- geotools builds locally for me with a 2.3.0 dependency
- http://hsqldb.org/doc/2.0/changelist_2_0.txt (do not see any
important regressions here)
No objection, just wondering, what do we owe the upgrade to?
I suspect the IP team has reviewed a newer version and/or older
version and has asked Tyler if it is possible to upgrade.
Checking ... GeoMesa used hsqldb 2.3 so it had been reviewed already
(not sure why they needed that version)
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
