Tested the binary download on macOS / Java 11 without problem. Windows testing (java 8 32-bit / windows service) starts up but showing the layer preview for spearfish produces:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM " http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";> <ServiceExceptionReport version="1.1.1" > <ServiceException code="InvalidSRS"> Error occurred decoding the espg code EPSG:4326 No code "EPSG:4326" from authority "European Petroleum Survey Group" found for object of type "IdentifiedObject". </ServiceException></ServiceExceptionReport> The logs folder has *wrapper.log* and *keepme.txt* but no *geoserver.log* Checking wrapper.log the problems start right away: INFO | jvm 1 | 2019/04/26 00:05:31 | 26 Apr 00:05:30 WARN [referencing.factory] - Unavailable authority factory: European Petroleum Survey Group INFO | jvm 1 | 2019/04/26 00:05:31 | 26 Apr 00:05:30 WARN [org.geoserver] - Error decode epsg code: EPSG:32633 INFO | jvm 1 | 2019/04/26 00:05:31 | org.opengis.referencing.NoSuchAuthorityCodeException: No code "EPSG:32633" from authority "European Petroleum Survey Group" found for object of type "IdentifiedObject". -- Jody Garnett On Thu, 25 Apr 2019 at 21:10, Jody Garnett <jody.garn...@gmail.com> wrote: > GeoServer release is ready for testing: > https://build.geoserver.org/geoserver/release/2.15.1 > -- > Jody Garnett > > > On Tue, 23 Apr 2019 at 08:05, Jody Garnett <jody.garn...@gmail.com> wrote: > >> Good morning all, looking at starting the release train (a few days late >> due to foss4gna conference). >> >> The most recent CITE tests have: >> >> version = 2.15-SNAPSHOT >> git revision = 6512081de52f22144da3914cdafac06174033280 >> git branch = origin/2.15.x >> build date = 23-Apr-2019 01:24 >> geotools version = 21-SNAPSHOT >> geotools revision = b5940536fca8378e546bc9f0aeb986c21be38e10 >> geowebcache version = 1.15-SNAPSHOT >> geowebcache revision = f05686d2752762758709029f1cc2fb1fbdcb5601/f0568 >> >> >> Any last minuet changes required? Speak now or wait for the next release >> ... >> >> I will be updating the release scripts so that README.html links are set >> via a build parameter (between latest, stable and maintenance) using the >> same approach as was done for GeoTools. >> >> There is an open bug about some of the required jars of the GeoTools >> binary release being missing that I will look out for. >> >> Torben I will ping you to upload GWC and GeoServer docs when ready >> (although we should teach build.geoserver.org to do that with a script). >> -- >> Jody Garnett >> >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
