> > GeoTools / GeoServer PMC meeting - 2025-05-20Attending -
Torben Barsballe - Gabriel Roldan - Jukka Rahkonen - Cécile Vuilleumier - Peter Smythe - Jody Garnett - Kevin Smith - Andrea Aime Actions from prior meetings: - [image: unchecked] gabe: some small update for dev guide, updating conf.py by hand no longer needed - [image: unchecked] Volunteer needed: postgis testing github workflow action - [image: unchecked] Angelos: Check if standards committee can request budget to certify GeoServer - [image: checked] Jody: Make a note on CITE sponsorship opportunities in the Q2 Dev update - [image: checked] Gabe: Review GeoTools PMD 7 Update (600 files!) Agenda - Adopt Maven Bill of Materials Pattern for GeoTools <https://github.com/geotools/geotools/wiki/Adopt-Maven-Bill-of-Materials-Pattern-for-GeoTools> proposal - OGC API Processes status - GS3 Updates - CITE no progress - Chit Chat Actions - [image: unchecked] gabe: submit bom proposal to gt-devel email list Adopt Maven Bill of Materials Pattern for GeoTools proposal One the first GS3 proposals: https://github.com/geotools/geotools/wiki/Adopt-Maven-Bill-of-Materials-Pattern-for-GeoTools - Not quite time critical, but also do not wish to hold up development - gt proposal process <https://docs.geotools.org/latest/developer/procedures/proposal.html>: - svn access for changes is granted within 3 days from the proposal - proposal is accepted ‘automatically’ within 15 days (unless objections are raised) - Trying this in first, before Java 17 LTS minimum, which will upgrade a massive amount of dependencies (in part to prep for JakartaEE) Use of BOM internally as well as externally: - gt-platform-dependencies bom, collecting dependency management - gt-bom that defines GeoTools artifacts - used internally to GeoTools also so no danger of being out of sync building notes: - when building local module in isolation, keep in mind need to `mvn install` the local bom Draft PR link <https://github.com/geotools/geotools/pull/5196/> discussion: - This will be great when updating jai-ext, the single change in GeoTools will ripple down to GWC and GeoServer, and the github integration workflows will test also - We focus on dependency management, but properties are included also, so some careful checking may be needed around “junit.version” and so on … OGC API Processes status Community module update demo: Service: Open API: Process: Execute: - Post a JSON document, to /execution - Get an “arrow” response, back a json response, linking to output - Or get back a “row” response, that includes the output directly - Also a KVP execution mode, works well for simple processes https://gs-main.geosolutionsgroup.com/geoserver/ogc/processes/v1/processes/JTS:buffer/execution?geom=POINT(0%200)&geom%5Btype%5D=application%2Fwkt&distance=10&response%5Bf%5D=application/json Discussion: - Classic OGCAPI wraps WPS etc… - job list is a security list what are they thinking :P - no post request to fetch data, only get - no chaining, being discussed as a draft “workflows” idea, define chain workflow using a POST, and then execute - Async: Uses HTTP header “Prefer: respond-async” to indicate Async execution - Do you like OGCAPI-Process? - Andrea - hard to implement, but likes ability to browse in HTTP, async mode is most useful in really world - Jukka - enjoying early draft in production Ideas: - If we have a javascript developer it would be nice to have an “execute” option when looking at a process - Conformance class is hard coded for now, would be nice to mark 1.1/conf/kvp-execute as DRAFT GS3 Updates So yeah: - GeoServer 2025 Q2 Developer Update <https://geoserver.org/behind%20the%20scenes/2025/05/13/developer-update.html> (blog communication) - https://github.com/geoserver/geoserver/wiki/GeoServer-3 - collected up some of the JakaraEE wiki pages here and we can update during implementation - Discussion thread for chit-chat, and folks working on it can introduce themselves there - https://discourse.osgeo.org/t/gs3-milestone-1-updates/147158 - ImageN kickoff meeting tomorrow, online code sprint next week Cecile: - OAuth2 update, looked at PR! - rebase and testing - works quite well, login with keycloak - role from geoserver, role from access token - This will be ‘done’ when all the existing community module tests to the new community module - This is the best record of what the old community module does; since not everything was documented - We know bearer-tokens are not covered also, used by front-end applications - Next steps: - Merge the PR as soon as possible! :D - Migrate tests from the old modules CITE no progress No update from OSGeo Chit Chat
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
