Skip to content

feat: embed mirthsync 3.7.0 and expose selective deployment (0.0.5) - #3

Merged
jessesaga merged 1 commit into
mainfrom
mirthsync-3.7.0
Sep 15, 2026
Merged

jessesaga merged 1 commit into
mainfrom
mirthsync-3.7.0

Conversation

@jessesaga

Copy link
Copy Markdown
Contributor

Summary

  • Embedded CLI bumped 3.5.1 → 3.7.0 (server + client POMs); plugin 0.0.5 in all four POMs. mirthsync 3.7.0 is on Clojars. Engine compatibility list untouched (4.5.2, 4.6.0).
  • Settings panel: "Deploy only changed channels" (--deploy-changed) and "Also deploy new channels" (--deploy-new), wired through presets (incl. the SETTING_KEYS serialization list), snapshot/restore, properties, argv. "Only changed" is exclusive with the other deploy boxes; "new" is enabled only with "changed".
  • README: engine versions, embedded CLI version, deploy options.

Verification

  • ./build.sh succeeds against the Clojars artifact; generated plugin.xml lists libs/mirthsync-3.7.0.jar, pluginVersion 0.0.5, runtime whitelist unchanged.
  • Independent review pass; findings fixed (preset key list was the blocker).
  • Smoke on OIE 4.6.0 with the zip installed via custom-extensions: POST /api/mirthsync/execute -V → 3.7.0; pull → push --deploy-changed (nothing pending) → edit → push (Deploying 1 channel(s)) → --deploy-new alone warns; /help lists both flags.
  • Swing panel is a human check with the externally signed build.

The plugin embeds the mirthsync CLI as a Maven dependency and calls its
mainFunc in-process; 0.0.4 still bundled 3.5.1. Bump the dependency to
3.7.0 in the server and client modules (its dependency list is identical
to 3.5.1, so the hand-maintained runtime whitelist still covers the
closure) and the plugin to 0.0.5 in all four POMs. Engine compatibility
(4.5.2, 4.6.0) is unchanged.

Settings panel gains "Deploy only changed channels" (--deploy-changed)
and "Also deploy new channels" (--deploy-new), mirrored through preset
defaults, the preset serialization key list, snapshot/restore, and
properties load/save. "Only changed" clears the other two deploy boxes
(mirthsync runs every deploy flag it is given and warns); "new" is
enabled only with "changed" and is cleared when it is not.

Smoke-tested on OIE 4.6.0: POST /api/mirthsync/execute reports 3.7.0
and the same push --deploy-changed sequence deploys exactly the edited
channel; /help lists both flags.
@jessesaga
jessesaga merged commit 6f7cfe7 into main Sep 15, 2026
2 checks passed
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.

2 participants