[Geoserver-devel] [JIRA] (GEOS-9897) JTS upgrade breaks geofence integration

GeoServer GeoServer Developer
,
1

Emanuele Tajariol created an issue

GeoServer / TaskGEOS-9897

JTS upgrade breaks geofence integration

Issue Type:

TaskTask

Affects Versions:

2.17.3, 2.18.0, 2.18.1, 2.17.4, 2.18.2

Assignee:

Emanuele Tajariol

Components:

GeoFence

Created:

10/Feb/21 4:24 PM

Environment:

GeoServer >=2.17.3
geofence-server with postgis backend

Priority:

HighHigh

Reporter:

Emanuele Tajariol

Since 2.17.3 JTS has been upgraded to 1.17.0
JTS 1.17 breaks API compatibility (see https://github.com/locationtech/jts/blob/master/doc/JTS_Version_History.md#api-changes-1)
This break happens within the postgis driver for hibernate spatial 1.1.3.1 used by GeoFence.
This means that if GeoFence runs as a standalone webapp, the JTS version will be the one declared within the GeoFence deps and everything will work. When GeoFence is run within GeoServer, it will use the GeoServer version, and hibernate spatial will break.

A new version of hibernate spatial (1.1.3.2) has been built with support to JTS 1.17.
Since GeoServer 2.17.x relies on GeoFence 2.4.6, a new release (2.4.6.1) has been done, using the updated hibernate-spatial version.

Version 2.18 will use the 3.4.6 as well, since next version brings in some changes in DTOs (SRID and areas)
Version 2.19 is using a geofence version that supports the SRID and area changes.

Pls also refer to https://github.com/geoserver/geofence/issues/166

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154-sha1:7cdb571)

Atlassian logo