Custom JVM only updated if version differs

[rbuehlma]

Getdown supports a custom jvm using java_location. This custom jvm is only downloaded if the version used to run getdown does not meet the version requirement (java_min_version, java_max_version).

In our project, we use jlink to build our own JVM. Even if the version number of the JVM does not change, it might include different modules. From my point of view, there should be an option to

• force the usage of the custom jvm (even if the version used to launch getdown would be ok)
• always update the jvm as soon as it has been updated on appbase

What is your opinion on this?

I guess this would mean that the jvm gets a line in the digest file and is updated similar to the other resources.

[sergiorussia]

simple workaround: change release file in your jre, set JAVA_VERSION to some non-existing version. then in your getdown.txt simply set java_min_version=<that version> and java_exact_version_required=true