Complete Guide to Installing Java on macOS Using Homebrew

Nov 21, 2025 · Programming · 11 views · 7.8

Keywords: Java | Homebrew | macOS | Installation Guide | Development Environment

Abstract: This article provides a comprehensive guide to installing Java development environment on macOS using the Homebrew package manager. Based on the latest Homebrew core repository updates, it covers the complete process from basic installation to system configuration, including Java version verification and symbolic link creation. With clear command-line examples and troubleshooting methods, it helps developers quickly set up their Java development environment.

Introduction

With the continuous development of the Homebrew package manager, the installation methods for Java have been constantly optimized. Since August 2022, Java has been officially included in Homebrew's core repository, significantly simplifying the process of installing Java on macOS. This article, based on the latest Homebrew practices, details how to configure the Java environment through simple command-line operations.

Homebrew Basic Preparation

Before starting the Java installation, ensure that Homebrew is properly installed and configured on your system. If not yet installed, you can install it using the following command:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

After installation, it is recommended to update Homebrew to ensure you get the latest package information:

brew update

Java Installation Process

Currently, the most direct way to install Java is using Homebrew's core command:

brew install java

This command will automatically download and install the latest version of OpenJDK. The installation process may take a few minutes, depending on network speed and system performance.

Installation Verification

After installation, you need to verify that Java has been installed correctly. Run the following command to check the Java version:

java -version

If the installation is successful, you should see output similar to the following:

openjdk 18.0.2 2022-07-19
OpenJDK Runtime Environment Homebrew (build 18.0.2+0)
OpenJDK 64-Bit Server VM Homebrew (build 18.0.2+0, mixed mode, sharing)

Common Issues and Solutions

In some cases, even if Java is successfully installed, the system may still fail to recognize the Java runtime environment. If you encounter the following error message when running java -version:

The operation couldn’t complete. Unable to locate a Java Runtime.
Please visit http://www.java.com for information on installing Java.

This indicates that the system requires additional configuration to recognize the Java installed via Homebrew. The solution is to create a symbolic link:

sudo ln -sfn /opt/homebrew/opt/openjdk/libexec/openjdk.jdk /Library/Java/JavaVirtualMachines/openjdk.jdk

This command links the Homebrew-installed Java to the system's standard Java Virtual Machines directory, enabling the system to correctly identify and use the Java environment.

Version Management and Multi-Version Support

While this article primarily focuses on installing the latest version of Java, Homebrew also supports installing specific versions. For example, if you need to install Java 11, you can use:

brew install openjdk@11

For multi-version management, you can switch between different Java versions by creating different symbolic links. This flexibility allows developers to easily switch between different Java environments based on project requirements.

Best Practice Recommendations

To ensure the stability and compatibility of your Java environment, it is recommended to follow these best practices:

Conclusion

Installing Java via Homebrew provides macOS developers with a simple and efficient way to configure their Java environment. As Homebrew's support for Java continues to improve, this method becomes increasingly reliable and convenient. By following the steps outlined in this article, developers can quickly set up a complete Java development environment and focus on application development rather than the tedious details of environment configuration.

Copyright Notice: All rights in this article are reserved by the operators of DevGex. Reasonable sharing and citation are welcome; any reproduction, excerpting, or re-publication without prior permission is prohibited.