Fixing ' is not on the classpath': A Comprehensive Guide to Resolving this JVM Error

When working with Java applications, you may encounter the error is not on the classpath. This error is often caused by misconfiguration, missing dependencies, or incorrect settings in your build environment. This comprehensive guide will help you identify, diagnose, and resolve this error in your Java projects.

Table of Contents

Understanding the Error

The is a part of the Java compiler, which is responsible for converting your Java source code into bytecode that can be executed by the Java Virtual Machine (JVM). When you encounter this error, it means that the Java compiler cannot be found on your classpath.

The classpath is a list of paths, directories, and JAR files that the JVM uses to find class files during runtime. When a class is not found on the classpath, it can lead to various errors, including the one mentioned above.

Common Causes of the Error

There are several possible reasons why you might encounter this error. Some of the most common causes include:

  1. Missing tools.jar: The tools.jar file, which contains the Java compiler, might be missing from your classpath or JDK installation.
  2. Incorrect JAVA_HOME or JDK_HOME: The environment variables JAVA_HOME and JDK_HOME might be pointing to the wrong locations, causing the compiler to be unavailable.
  3. Misconfiguration in the build tool: The build tool you are using might be misconfigured, leading to an incorrect classpath setup.

Step-by-Step Solution

To resolve the is not on the classpath error, you can follow these steps:

Step 1: Verify the JDK Installation

Ensure that you have a valid JDK installation. You can check this by running the following command in your command prompt or terminal:

javac -version

If the command returns a valid version number, then your JDK installation is correct. If not, you need to download and install the JDK.

Step 2: Check the JAVA_HOME and JDK_HOME Environment Variables

Ensure that the JAVA_HOME and JDK_HOME environment variables are set correctly. These variables should point to the root directory of your JDK installation.

To check the value of these variables, run the following commands:

echo %JAVA_HOME% (Windows)
echo $JAVA_HOME (Unix-based systems)

echo %JDK_HOME% (Windows)
echo $JDK_HOME (Unix-based systems)

If the values are incorrect, update your environment variables to point to the correct JDK installation directory.

Step 3: Verify the Presence of tools.jar

Check whether the tools.jar file is present in the lib directory of your JDK installation. If the file is missing, you can try reinstalling the JDK or manually downloading the tools.jar file from a trusted source and placing it in the correct directory.

Step 4: Update the Build Tool Configuration

Ensure that your build tool (e.g., Maven, Gradle, or Ant) is correctly configured to include the Java compiler in the classpath. Check your build configuration files (e.g., pom.xml, build.gradle, or build.xml) and verify that the correct JDK version and classpath settings are used.


1. Can I use the JRE instead of the JDK to compile my Java code?

No, the JRE (Java Runtime Environment) does not include the Java compiler. You need the JDK (Java Development Kit) to compile Java code.

2. How do I set the JAVA_HOME and JDK_HOME environment variables?

On Windows, you can set environment variables by following these steps:

  1. Right-click on "This PC" or "Computer" and select "Properties."
  2. Click on "Advanced system settings" in the left pane.
  3. Click on the "Environment Variables" button.
  4. In the "System Variables" section, click "New" and add the desired variable name and value.

On Unix-based systems, you can set environment variables by adding the following lines to your shell configuration file (e.g., ~/.bashrc, ~/.zshrc, or ~/.bash_profile):

export JAVA_HOME=<path-to-jdk>
export JDK_HOME=<path-to-jdk>

3. How do I add the tools.jar to my classpath?

You can add the tools.jar to your classpath by updating your build tool configuration or by manually adding the file to the classpath when running your application. For example, you can use the -cp flag when running your Java application:

java -cp <path-to-tools.jar>:<other-classpath-entries> com.example.MainClass

4. Can I use a different Java compiler instead of

Yes, there are alternative Java compilers available, such as the Eclipse Compiler for Java (ECJ). However, you need to ensure that your build tool is configured to use the desired compiler and that it is compatible with your project's requirements.

5. How can I permanently add tools.jar to my classpath?

You can permanently add tools.jar to your classpath by updating your system's environment variables. On Windows, you can add the tools.jar to the CLASSPATH variable in the "Environment Variables" dialog. On Unix-based systems, you can add the following line to your shell configuration file:

export CLASSPATH=<path-to-tools.jar>:$CLASSPATH

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.