GS GF Compatibility matrix

Here a compatibility matrix for GS and GF versions.
Strikethrough versions will behave badly.

GeoServer	JTS	Declared GF	GF needed for PG	GF needed for H2
2.22 (main)	1.19.0	3.6.0
2.21.x	1.18.2	3.5.1
2.21.0-1	1.18.2	3.5.0
2.20.6	1.18.2	3.5.1
2.20.0-5	1.18.2	3.5.0	3.5.0	3.5.0
2.19.0-6	1.18.1	3.5.0	3.5.0	3.5.0
2.18.x	1.17.1	3.4.6.1	3.4.6.1	3.4.6.1
2.18.2	1.17.1	3.4.6	3.4.6.1	3.4.6 or 3.4.6.1
2.18.1	1.17.1	3.4.6	3.4.6.1	3.4.6 or 3.4.6.1
2.18.0	1.17.1	3.4.2	3.4.6.1	3.4.6 or 3.4.6.1
2.17.5 (last)	1.17.0	3.4.6.1	3.4.6.1	3.4.6 or 3.4.6.1
2.17.4	1.17.0	3.4.6	3.4.6.1	3.4.6 or 3.4.6.1
2.17.3	1.17.0	3.4.6	3.4.6.1	3.4.6 or 3.4.6.1
2.17.2	1.16.1	3.4.6	3.4.6	3.4.6
2.17.1	1.16.1	3.4.6	3.4.6	3.4.6
2.17.0	1.16.1	3.4.6	3.4.6	3.4.6

• GeoServer, from 2.17.3, depended from a newer JTS version. This change causes errors in hibernate-spatial when GeoFence is running in embedded mode using PostGIS.
  hibernate-spatial issue was solved by recompiling it against JTS 1.17.0. This recompiled version is hibernate-spatial-postgis-1.1.3.2.jar.
  In order to fix the dependencies in GeoServer, GeoFence version 3.4.6.1 was released.
  Please note that 3.4.6.1 differs from 3.4.6 only in the hibernate-spatial dependency, so if you need to fix the postgis issue in a GeoServer 2.17.3, 2.17.4, 2.18.x(x<3), you only need to update hibernate-spatial-postgis to version 1.1.3.2, leaving the GeoFence jars you already have in place.

• API Changes: GeoFence version was bumped to 3.5.x. Related GeoServer client part was introduced on master 2.19.0.

  • #161 introduced an API change (SRID definition in area WKT)
  • #163 introduced an API change (Clip area and area restriction mode)

• GeoFence 3.4.7 and 3.4.8 were deprecated in favor of 3.5.0, because they suffered of the JTS upgrade compatibility issue.