Previous versions of macOS use the current value of the JAVA_HOME environment variable to launch the appropriate version of any commands from the JDK bin folder. This was presumably handled by some magic in the JDK commands that are installed in /usr/bin.
On Big Sur beta 7 I am no longer seeing this behaviour. I always get the latest installed version of the JDK command regardless of what I set JAVA_HOME to.
I usually run a script to set JAVA_HOME based on the output of
(where ??? is related with the JDK version). The java_home command is working as expected and I am sure that the JAVA_HOME environment variable is correctly set.
I've submitted a report with Feedback Assistant, but I wonder if others can confirm this is a reproducible problem. Is there a workaround?
On Big Sur beta 7 I am no longer seeing this behaviour. I always get the latest installed version of the JDK command regardless of what I set JAVA_HOME to.
I usually run a script to set JAVA_HOME based on the output of
Code Block /usr/libexec/java_home -v ???
(where ??? is related with the JDK version). The java_home command is working as expected and I am sure that the JAVA_HOME environment variable is correctly set.
I've submitted a report with Feedback Assistant, but I wonder if others can confirm this is a reproducible problem. Is there a workaround?