Skip to content

Derive MEOS catalog in the javadoc workflow#45

Merged
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:fix/javadoc-provision-catalog
Jul 10, 2026
Merged

Derive MEOS catalog in the javadoc workflow#45
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:fix/javadoc-provision-catalog

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

The push-only deploy_javadoc.yml workflow broke on main after the catalog stopped being committed: mvn compile runs generate-meos-facade, which reads codegen/input/meos-idl.json and now fails with FileNotFoundException.

This provisions the catalog the same way maven.yml already does — via the shared provision-meos action — so the javadoc build is consistent with the main build. It runs build-libmeos: "false" (catalog-only) because javadoc compiles the sources but never executes them, so the native library is not needed here.

Fixes the red Deploy Javadoc to GitHub Pages run on main.

The javadoc build compiles jmeos-core, which runs the generate-meos-facade
step and reads codegen/input/meos-idl.json. That file is no longer committed
(it is derived in CI and gitignored), so the push-only javadoc workflow failed
with FileNotFoundException. Provision it via the shared provision-meos action
exactly as maven.yml does, catalog-only since javadoc never runs the library.
@estebanzimanyi estebanzimanyi merged commit a88df27 into MobilityDB:main Jul 10, 2026
1 check passed
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.

1 participant