Skip to content

[GEOS-11624] Split geopackage extension into three (sub)modules#7965

Merged
aaime merged 1 commit intogeoserver:mainfrom
woutergd:features/geopkg-output-improvements
Dec 9, 2024
Merged

[GEOS-11624] Split geopackage extension into three (sub)modules#7965
aaime merged 1 commit intogeoserver:mainfrom
woutergd:features/geopkg-output-improvements

Conversation

@woutergd
Copy link
Contributor

@woutergd woutergd commented Oct 18, 2024

As I am working on implementing the Geopackage Output extension into the Geoserver Cloud project, I found out that this was not easily possible as it was a single module that imported the GWC, WMS and WFS modules. To make it a better fit, hereby I propose the changes to split this extension into three separate modules: a wms and wfs module, and a core module that support both of them.

Checklist

For core and extension modules:

  • New unit tests have been added covering the changes.
  • Documentation has been updated (if change is visible to end users).
  • The REST API docs have been updated (when changing configuration objects or the REST controllers).
  • There is an issue in the GeoServer Jira (except for changes that do not affect administrators or end users in any way).
  • Commit message(s) must be in the form [GEOS-XYZWV] Title of the Jira ticket.
  • Bug fixes and small new features are presented as a single commit.
  • Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

@woutergd woutergd changed the title Split geopackage extension into three submodules Split geopackage extension into three (sub)modules Oct 18, 2024
@aaime
Copy link
Member

aaime commented Nov 25, 2024

Sure, I don't see a problem here. By looking at ext-geopkg-output.xml it seems the assembly will still catch the right jar files. @jodygarnett what do you think?=

@jratike80
Copy link
Contributor

Will the WFS submodule take care of the OGC API Features GeoPackage output if that will be supported in the future?

@aaime
Copy link
Member

aaime commented Nov 25, 2024

It should... in theory even today, when installing both the OGC API features package and the Geopackage output format, the GeoPackage format should become available in OGC API features. But I haven't tried.

@jodygarnett
Copy link
Member

It should be fine, a bit of a pain to have more jars; but it is maven ...

@woutergd
Copy link
Contributor Author

Sorry, had not enough time last weeks to continue on this PR. Good to hear that these changes are not expected to be an issue.

I noticed that I have for some strange reason failures on the JDK 17 and 21 builds, is there someone who can point me in the right direction to resolve these build errors? I will try also to fix this week the merge conflicts, so this PR can move forward.

@aaime
Copy link
Member

aaime commented Nov 26, 2024

You can safely ignore those failures, they are happening sometimes on the Github actions but we cannot reproduce them on developer machines. But please make sure you rebase this PR on top of the latest main branch, as we try to mitigate those failures over time by giving tests more leniency (some are time based, others will retry on lock failures, and so on).

@woutergd woutergd changed the title Split geopackage extension into three (sub)modules [GEOS-11624] Split geopackage extension into three (sub)modules Nov 26, 2024
@woutergd
Copy link
Contributor Author

@aaime thanks for the info. I rebased this PR, and also created a JIRA-issue as was suggested to me in Discourse as something that was required to provide a PR.

I noticed however that after the rebase I have different / new tests that are failing. Are these also known? Otherwise I will make some time this week to investigate what the issue is for these build errors.

@woutergd woutergd marked this pull request as ready for review November 27, 2024 14:16
@aaime
Copy link
Member

aaime commented Dec 9, 2024

Had a look, everything seems to check out. Merging.

@aaime aaime merged commit 03125b3 into geoserver:main Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants