Hi,
if we want geos-175 to be fixed, we'll need to upgrade our dependencies
to geotools 2.2.1, the bug is really in geotools.
See: http://jira.codehaus.org/browse/GEOS-715
Cheers
Andrea
aaime@anonymised.com wrote:
Hi,
if we want geos-175 to be fixed, we'll need to upgrade our dependencies
to geotools 2.2.1, the bug is really in geotools.
See: http://jira.codehaus.org/browse/GEOS-715
That is fine, we can upgrade minor point releases of geotools with no problem, no need to ask.
Chris
Cheers
Andrea-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1003,4522a199213872081064789!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes ha scritto:
aaime@anonymised.com wrote:
Hi,
if we want geos-175 to be fixed, we'll need to upgrade our dependencies
to geotools 2.2.1, the bug is really in geotools.
See: http://jira.codehaus.org/browse/GEOS-715That is fine, we can upgrade minor point releases of geotools with no problem, no need to ask.
Ok, then it's time to start pushing for a gt2 2.2.1 release
Cheers
Andrea