Document how to regenerate the binding by hand - #44
Merged
estebanzimanyi merged 1 commit intoJul 22, 2026
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gives
GENERATION.mdthe commands it describes, so the chain can be run outside CI.The document states the policy and draws the input chain, but carries no command, so reproducing a generation means reading
.github/workflows/maven.ymland theexec-maven-pluginblock inflink-processor/pom.xmlto 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 coordinatesflink-processor/pom.xmlresolves), then stage the catalog totools/meos-idl.jsonand build. It also states the two properties the smoke tests need —meos.lib.dirto locatelibmeos.so, andmeos.enabledto turn them on.The commands mirror what CI already does, so the two paths stay the same procedure.