Add a one-command refresh for the JVM consumers - #77
Merged
estebanzimanyi merged 2 commits intoJul 28, 2026
Conversation
…s.sh The libmeos build and catalog parse lived inline in the provision-meos composite action, and were transcribed again as prose into every GENERATION.md "regenerate by hand" section, so the CI path and the by-hand path could drift. Move that recipe (configure, build, install, parse) into tools/provision-meos.sh and have the action call it, so there is one definition instead of several: a developer refreshing the chain runs the same script CI does. The action keeps only the runner bootstrapping around it (checkout, Python, apt). Behaviour is unchanged.
A MobilityFlink, MobilitySpark or MobilityKafka developer refreshing their facades against the latest MEOS API otherwise walks four repos by hand. This runs the whole chain from one command: MobilityDB -> provision-meos.sh (catalog + libmeos) -> JMEOS jar -> facades It composes the per-leg scripts that already exist -- provision-meos.sh, then JMEOS regen-from-catalog.sh, then the consumer own Maven build -- and adds no derivation of its own, only the sequencing and the sibling checkouts, so it cannot drift from CI. Siblings default to their latest upstream default branch; --mdb / --jmeos point at an existing checkout to refresh against a MEOS branch still under development. Each consumer keeps a few lines in tools/refresh.conf (ENGINE, BUILD_DIR, JMEOS_COORDS, BUILD_CMD) for its last leg, and a thin tools/refresh-from-master.sh wrapper that locates this script and calls it.
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.
What
tools/refresh-jvm-chain.shruns the whole JVM chain from one command, so a MobilityFlink, MobilitySpark or MobilityKafka developer refreshes their facades against the latest MEOS API without walking the four repos by hand:Why
The chain composes the per-leg scripts that already exist —
provision-meos.sh(added in the base PR), thenJMEOS/regen-from-catalog.sh, then the consumer's own Maven build. It adds no derivation of its own, only the sequencing and the sibling checkouts, so it cannot drift from CI.Interface
--consumer <path>— the JVM consumer repo to refresh (hastools/refresh.conf).--mdb <path>/--jmeos <path>(or$MDB/$JMEOS) point at an existing checkout on any branch, to refresh against a MEOS branch still under development.--families,--skip-tests,--force,--work-dir; a rebuild-skip stamp keyed on both the MobilityDB commit and the family flags.tools/refresh.conf:ENGINE, the MavenBUILD_DIR, theJMEOS_COORDSthe build resolves the jar as, and theBUILD_CMD. Each consumer also carries a thintools/refresh-from-master.shwrapper that locates this script and calls it.Dependency
The base is the
provision-meos.shextraction PR, which adds the script this composes; the diff carries both commits. The consumer-siderefresh.conf+ wrapper are per-repo in MobilityFlink / MobilitySpark / MobilityKafka.Proof
A local run over MobilityFlink derives libmeos + catalog, builds the JMEOS jar, and regenerates the Flink facades: 116 facade classes / 4136 methods, and the
mobility-flink-bindingmodule builds.