Coursier-installed application JRE requirement

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…

1 Like

Thinking about it, I’m not sure how this could be made to work anyway.

Unless the policy would be to ratchet up the installed JRE to the maximum required over all installed applications, there would have to be some coupling between installed applications and their required JREs.

I’m not sure how that would work with the usual case of an independently installed JRE being installed globally.

I’ll stick with JRE 17 and stop worrying about this.