The hard way: Figure out you're on a mac (which is now easier os.name returns Mac OS X, or just check for the existence: Files.isExecutable(Paths.get('/usr/bin/sw_vers'))), and then use ProcessBuilder to execute /usr/bin/sw_vers, picking up all output into a big string, and then parse it. You could add a mapping: Mac OS X/10.16 → Mac OS Big Sur in this table. These would map name/version pairs to rendering strings, falling back to just printing the name string and the version string, concatenated, verbatim. Acknowledge that os.name and os.version give you (rather arguably) useful intent and not so much official names, and therefore, write some mappings. The easy one is to just write mapping code. This leaves you with the challenge of: Okay, great, I can use System.getProperty('os.name') to get the globally agreed upon keyword that means unix-like Mac OS, and os.version for a string I can break into bits to figure out some nebulous batch of capabilities, but what if I need the actual name of the OS to e.g. If you want to point at an OS transition that might warrant the entirely nebulous choice to consider it a 'major change', surely it was the one to catalina, as that made by far the largest changes (including removing support for 32-bit entirely) in the last bunch of releases. There is no meaningful difference between the transition between big sur and catalina, other than the fact that apple made a marketing decision. The same applies, to a lesser degree, to version 10.16: The thing before the dot is not so much 'this is how the OS identifies itself' and more a 'globally agreed upon versioning scheme for Mac OS, identifying a wide and ill defined set of capabilities'.

Changing it would just break stuff needlessly.

At this point, the name Mac OS X is not so much 'the name of the OS' as a 'globally agreed upon keyword identifying that unix-based mac operating system', where I mean globally literally (as in, 'around the planet', not 'across your source base/VM'). You can file a bug if you want, but I bet it'll be denied. Make sure that the class name and file name are the same.Can confirm this is still happening on adoptopenjdk14, as well as openjdk early access build for j16. Now write the first Java program as shown below, save the program as HelloWorld.java and exit the editor. In this step, we will write, compile, and execute our first program in Java using the standard Hello World example. This is all about installing JDK 8 on Mac systems including macOS Sierra, High Sierra, Mojave, and Catalina.

Java 8 mac os x