Kinetic Merge is packaged as a Coursier executable, so an end-user can do a cs install --contrib kinetic-merge
and off they go…
… only Kinetic Merge requires a JRE >= 17.
Now if you have Coursier installed in the first place, I suspect it will make sure that there is a JRE >= 17 on your system, and install JRE 17 if not. So all is well.
What I’m not sure about is what the story is going forward. If I’m adventurous and bump the minimum JRE required by Kinetic Merge up to, say, 21 LTS, can I tell Coursier to ensure that such a JRE is present when it installs or updates Kinetic Merge for subsequent releases?
I had a quick look through the application descriptor documentation, but nothing jumped out at me about this…