Mark noted:

I just noticed, while updating a war overlay build, that GeoServer 2.25.3
> depends on snapshot versions for both GWC (1.25-SNAPSHOT) and GF
> (3.7-SNAPSHOT) [geofence]
>

> see:
> https://repo.osgeo.org/repository/release/org/geoserver/geoserver/2.25.3/geoserver-2.25.3.pom
>

> This could lead to undeterministic behaviour when rebuilding the war file
> for war overlays, Geofence being an extension there is little risk, but the
> gwc jars are actually packaged in the war file.
>

*Geowebcache 1.25.2*

The bin download contains:

gwc-wmts-1.25-SNAPSHOT.jar
gwc-core-1.25-SNAPSHOT.jar
gwc-diskquota-core-1.25-SNAPSHOT.jar
gwc-diskquota-jdbc-1.25-SNAPSHOT.jar
gwc-georss-1.25-SNAPSHOT.jar
gwc-gmaps-1.25-SNAPSHOT.jar
gwc-kml-1.25-SNAPSHOT.jar
gwc-rest-1.25-SNAPSHOT.jar
gwc-tms-1.25-SNAPSHOT.jar
gwc-ve-1.25-SNAPSHOT.jar
gwc-wms-1.25-SNAPSHOT.jar


GeoServer 2.25.3 was tagged July 19, and would of included a single
geowebcache commit:

Update Jackson 2 libs from 2.17.1 to 2.17.2
> <https://github.com/GeoWebCache/geowebcache/commit/70b38c615f940b311e4756224a66013d6d84bb81>
>

The GeoServer pom.xml already contains this information:

<jackson2.version>2.17.2</jackson2.version>
>


*guidance: *So anyone using war overlay is advised to provide an explicit
dependency on geowebcache 1.25.2, and everything should be fine.
I do not see the need to re-release 2.25.3 at this time.


*GeoFence*

geofence-3.5.x-nightly build is broken
geofence-3.6.x-nightly build is broken
geofence-master ... this must be 3.7-SNAPSHOT? Confirmed

Checking history:

   - There were some updates on August 26, mostly updating version numbers.


   - The key subsequent change on Nov 10 was removing the gui module in
   order to build with JDK 11
   - Prior to this 3.7.1 was released Nov 9 2023 ...


I do not feel comfortable providing guidance on this one.

Jody
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to