Currently alternatives are used for determining Java home if JAVA_HOME is not set (as environment variable or in none of config files), which is default system setting. But this can break system if user decides to install third-party JDK and point alternatives to it.
I think that we should set JAVA_HOME in /etc/java/java.conf to sane default, which will effectively kill code for supporting alternatives and allow it to be removed from java-functions. Users will be able to customize JVM used in config files, which should be easier than changing multiple alternatives.
Currently alternatives are used for determining Java home if JAVA_HOME is not set (as environment variable or in none of config files), which is default system setting. But this can break system if user decides to install third-party JDK and point alternatives to it.
I think that we should set JAVA_HOME in /etc/java/java.conf to sane default, which will effectively kill code for supporting alternatives and allow it to be removed from java-functions. Users will be able to customize JVM used in config files, which should be easier than changing multiple alternatives.