Skip to content

Document how to regenerate the binding by hand - #42

Merged
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:docs/generation-runnable
Jul 22, 2026
Merged

Document how to regenerate the binding by hand#42
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:docs/generation-runnable

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

Gives GENERATION.md the commands it describes, so the chain can be run outside CI.

The document states the policy and names the two inputs — the catalog and the JMEOS jar — but carries no command, so reproducing a generation means reading .github/workflows/maven.yml and the exec-maven-plugin block in pom.xml to recover what CI does.

It now carries the three steps: derive libmeos and the catalog from the MobilityDB commit being targeted, build the JMEOS jar against that catalog and install it as org.jmeos:meos:1.0 (the coordinates pom.xml resolves), then stage the catalog to tools/meos-idl.json and build. It also states that LD_LIBRARY_PATH is how the tests locate libmeos.so.

The commands mirror what CI already does, so the two paths stay the same procedure.

The generation contract describes the policy and the inputs, but carries no
command, so running the chain outside CI means reconstructing it from the
workflow and the pom.

Give the steps: derive libmeos and the catalog from the MobilityDB commit being
targeted, build the JMEOS jar against that catalog and install it under the
coordinates this build resolves, stage the catalog, and build. State how the
tests locate libmeos.
@estebanzimanyi
estebanzimanyi merged commit 3231038 into MobilityDB:main Jul 22, 2026
1 check passed
@estebanzimanyi
estebanzimanyi deleted the docs/generation-runnable branch July 22, 2026 14:33
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