Mystery solved, I think we are good to go ahead with the 2.20.3 release, I
will check back tomorrow and we can announce on monday.
--
Jody Garnett
On Thu, 24 Feb 2022 at 13:07, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Ok, I understand now. I have tested the Windows
Whew!
There was a change made to startup.bat for this release:
- https://osgeo-org.atlassian.net/browse/GEOS-10316
-
https://github.com/geoserver/geoserver/pulls?q=is%3Apr+GEOS-10316+is%3Aclosed
I do not see any change there that could explain your challenge, is it
possible you had the 2.20-RC
Ok, I understand now. I have tested the Windows installer with 2.20-RC and the
installer sets GEOSERVER_HOME environment. Since that I have been running the
RC version on this computer because startup.bat checks GEOSERVER_HOME. That was
not a problem for me earlier because a) normally I do not
Steve Ikeoka (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ac68be705-e740-4b23-b796-c04c7a01eaf3
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZTIzYTY1NTFiOGRkNGEzY2IxZGNlZmM0OGY2ZTgxNTYiLCJwIjoiaiJ9
) / Bug (
Hi Jody,
Yes, I have correct zip, but from the logs I found this entry:
2022-02-24 20:56:13.307:INFO:oejdp.ScanningAppProvider:main: Deployment monitor
[file:///C:/ohjelmat/gs20rc/GeoServer/webapps/] at interval 1
So the startup.bat from gs 2.20.3 decided to use something from an older
Jukka:
I downloaded geoserver-2.20.3-bin.zip and see the server status page
reporting:
Build Information
> GeoServer Version
> 2.20.3
> Git Revision
> 8cca82dc95b5609476f4fe9208e9e61ba5ff7c82
> Build Date
> 23-Feb-2022 17:51
> GeoTools Version
> 26.3 (rev
Something seems wrong then, as the windows installer was also sent 2.20-RC
as a parameter.
--
Jody Garnett
On Wed, 23 Feb 2022 at 23:58, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Hi,
>
>
>
> I tried bin-zip on Windows 10 with OpenJDK 11. I did not notice any
>
On Wed, Feb 23, 2022 at 6:55 AM Gabriel Roldan
wrote:
> Hi,
>
> I'm getting a build failure on `main`, apparently only if the old teradata
> jar is not in the local maven repo (e.g. rm -rf
> ~/.m2/repository/org/geoserver first).
>
> And wonder why the builds didn't fail for
>
