Skip to content

Derive MEOS catalog in the javadoc workflow #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
estebanzimanyi merged 1 commit into from
Jul 10, 2026
Merged

Derive MEOS catalog in the javadoc workflow #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions .github/workflows/deploy_javadoc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,23 @@ jobs:
- name: Set up Maven
run: mvn -B wrapper:wrapper

# Derive the MEOS catalog from MobilityDB in CI — it is no longer committed.
# Catalog-only (build-libmeos: false): javadoc compiles the sources but never
# runs them, so the native libmeos is not needed here.
- name: Provision MEOS catalog
id: provision
uses: MobilityDB/MEOS-API/.github/actions/provision-meos@master
with:
mobilitydb-ref: master
build-libmeos: "false"

# Stage the derived catalog where FunctionsGenerator reads it at build time.
# The catalog is gitignored — it only ever exists as a build artifact.
- name: Stage the derived catalog for the generator
run: |
mkdir -p codegen/input
cp "${{ steps.provision.outputs.catalog-path }}" codegen/input/meos-idl.json

- name: Build sources
run: mvn -B -DskipTests compile
# Compiles the codegen module and generates functions/GeneratedFunctions.java, so the
Expand Down
Loading