Add a one-command refresh against upstream MEOS - #27
Merged
estebanzimanyi merged 2 commits intoJul 28, 2026
Conversation
MobilityKafka built the JMEOS jar through its own build-jmeos.sh and depended on it as com.mobilitydb:jmeos:1.4.0, while MobilitySpark and MobilityFlink build JMEOS main directly and install the jar as org.jmeos:meos:1.0. Adopt the same build and coordinates: CI checks out JMEOS, builds it against the provisioned catalog and libmeos, and installs jar/JMEOS.jar as org.jmeos:meos:1.0; the binding depends on those coordinates; the tests load libmeos from /usr/local/lib where provision-meos installs it. build-jmeos.sh is removed; GENERATION.md, README and the benchmark doc describe the shared build.
tools/refresh-from-master.sh refreshes the MeosOps* facades against upstream MEOS in one command: it runs the shared MEOS-API refresh-jvm-chain.sh over this repo, deriving libmeos and the catalog from MobilityDB master, building the JMEOS jar, and regenerating the facades. tools/refresh.conf holds this consumer last leg (the repo-root module, the org.jmeos:meos:1.0 coordinates, the mvn command). GENERATION.md leads with the one-liner; .gitignore excludes the .meos-chain scratch.
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-from-master.shrefreshes theMeosOps*facades against upstream MEOS in one command:It runs the shared
MobilityDB/MEOS-APIrefresh-jvm-chain.shover this repo — deriving libmeos and the catalog from MobilityDB master, building the JMEOS jar, and regenerating the facades — so a developer runs one command instead of walking four repos by hand. Options pass through (e.g.--mdb ~/src/MobilityDB,--skip-tests).Files
tools/refresh.conf— this consumer's last leg: the repo-root Maven module, theorg.jmeos:meos:1.0jar coordinates, and themvn … clean testcommand.tools/refresh-from-master.sh— the thin wrapper that locates the shared script (cloning MEOS-API master the first time) and calls it. Byte-identical to the one in MobilityFlink and MobilitySpark.GENERATION.mdleads with the one-liner..gitignoreexcludes the wrapper's.meos-chain/scratch dir.Dependency
The base is the JMEOS-build uniformization PR (which switches the jar coordinates to
org.jmeos:meos:1.0); the diff carries both commits.