Re: [Geoserver-devel] ResourceStore API workparty

Jody, My apologies if I sound or have sounded agitated in this discussion. I do hope we find a solution. Thanks for the analysis I believe we are now working on the same problem: clarifying api design Yes, I share your goal but we don't seem to find a way to agree? I have done a proposal

Re: [Geoserver-devel] who has access to geoserver-docs.s3-website.eu-south-1.amazonaws.com?

We do not have access to that system which is why we move to osgeo hosting for stuff. Do you wish to add that jar to our website? Or upload to osgeo maven repo? Jody On Fri, Aug 4, 2023 at 2:44 AM Ian Turton wrote: > Currently the LDAP security tutorial points to a demo ldap system in a jar >

[Geoserver-devel] who has access to geoserver-docs.s3-website.eu-south-1.amazonaws.com?

Currently the LDAP security tutorial points to a demo ldap system in a jar that is stored at http://geoserver-docs.s3-website.eu-south-1.amazonaws.com/acme-ldap-1.0.jar - as a fix for https://osgeo-org.atlassian.net/browse/GEOS-11092 I've rebuilt the jar to work with Java 11 but the build system

[Geoserver-devel] [JIRA] (GEOS-11095) Bump git-commit-id-plugin 4.0.3 -> 4.9.10

Roar Brænden ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bda18abeee9a94b12bda564 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiODFiNTdmNGEzNzU0NDQ1Y2FhNDM1MmEyYWFlMDAxYTAiLCJwIjoiaiJ9 ) / Improvement (