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.25	1.19.0	3.7-RC
2.24.0-x	1.19.0	3.7-RC
2.23.0-x	1.19.0	3.6.0
2.22.0-x	1.19.0	3.5.1
2.21.2-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-x	1.18.1	3.5.0	3.5.0	3.5.0
2.18.4-x	1.17.1	3.4.6.1	3.4.6.1	3.4.6.1
2.18.3	1.17.1	3.5.0
2.18.1-2	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.

A note about main and master branches

Please disregard the master branch, since dev branch is main.

master evolved (with breaking changes for the standalone version) from the 3.4, but it was never used (there are no tags on it). Its "3.5" version in pom file was the next in line version from 3.4, but it was never released. The "real" (released) 3.5 tags are on main, not master.

When github introduced the main branch, we created main on the GeoFence branch that at that time was the most advanced, that is 3.5.x.

---

Here a coarser version match list, also reporting older versions:

GeoFence	GeoServer	Main changes
3.5.x - nightly: 3.5.x	2.19.x (client) (embedded)	DTO changes in restricted area: wkt, clip
3.4.x - stable: 3.4.6.1	2.18.x (client) (embedded) 2.17.x (client) (embedded)	JTS Version update Minor DTO changes
3.3.x		LDAP improvements Minor DTO changes
3.2.x	2.12 2.11 2.10 2.9	Spring 4, JDK 8
3.1.x	>=2.8.2	Handle Workspace admin (feature for embedded version only)
3.0.x	2.8.0, 2.8.1	GeoFence embedded into GeoServer (Only for older 2.8 releases; Not recommended)
2.2.x	2.7 2.6