All my pain points were around infrastructure and libraries.įoolishly, I didn't take notes during the upgrade process, so this is just what I remember and can glean from my Git history. Issues with the module system aside, the focus of the Java team on compatibility of the language itself has been nearly flawless as usual. Note that the codebase itself did not actually need changing for the new JDK version. The hope is it might help some people who weren't aware of some of these issues. It's just a list of some things I tripped over on the way to upgrading my own JDK project. Select the Java version you want to use as the default from the list of installed Java versions.Ĭlick on the 'OK' button to close the 'Java Applet Runtime Settings' window.This is isn't a step-by-step guide on how to upgrade your JDK.

Open the 'System Preferences' pane by clicking on the Apple icon in the top left corner of your screen and selecting 'System Preferences'.Ĭlick on the 'Java' icon in the 'System Preferences' pane.Ĭlick on the 'Java' tab in the 'Java Control Panel' window that appears.Ĭlick on the 'View' button in the 'Java Applet Runtime Settings' section. To change the default Java (JDK) version on macOS using the 'System Preferences' pane, follow these steps: Method 3: Using the 'System Preferences' pane

If you want to set the default Java version system-wide, you can modify the /etc/paths file instead. bashrc file will only affect the current user. Verify the default Java version by running the command java -version in the terminal.

Run the command source ~/.bash_profile or source ~/.bashrc to apply the changes.

Export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)

Current jdk version