How to Resolve 'Java 11 or More Recent is Required to Run' Error in Visual Studio Code When Using JDK 8

How can I fix the 'Java 11 or more recent is required to run' error in Visual Studio Code while using JDK 8?

This article addresses the common issue experienced in Visual Studio Code (VS Code) where a project configured to use JDK 8 encounters an error stating that 'Java 11 or more recent is required to run.' We'll explore the potential causes of this issue and outline effective solutions to ensure that VS Code recognizes your JDK 8 installation correctly.

{
    "java.configuration.updateBuildConfiguration": "disabled",
    "java.home": "/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home",
    "java.configuration.runtimes": [
        {
            "name": "JavaSE-1.8",
            "path": "/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home",
            "default": true
        },
        {
            "name": "JavaSE-11",
            "path": "/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home"
        }
    ]
}

Causes

• Configuration settings in VS Code may not be correctly pointing to your JDK 8 installation.
• The Java extension in VS Code may have been updated and is enforcing a minimum Java version requirement.
• Workspace settings or global settings may conflict, leading to the detection of an unsupported JDK version.

Solutions

• Open your `settings.json` in VS Code and ensure that the `java.home` path is correctly set to your JDK 8 installation path. Also, verify that the path is valid.
• Check the `java.configuration.runtimes` section for any inconsistencies or missing configurations; ensure the path to JDK 8 is the default runtime.
• Update or reinstall the Java extensions in VS Code, as they could have been modified to require a newer Java version.
• If issues persist, try creating a new workspace with just the essentials, setting it up to use just JDK 8, and then gradually adding back your project configurations.

Mistake: Incorrectly setting the `java.home` path leading to a non-existent or unexpected JDK version.

Solution: Double-check the actual installation path of JDK 8 and make sure it is correctly referenced in your `settings.json`.

Mistake: The presence of multiple JDKs on the system can create conflicts.

Solution: Remove any unnecessary or conflicting JDK installations, or ensure the correct one is prioritized in your PATH and settings.

Mistake: Forgetting to restart VS Code after making changes to configuration files.

Solution: Always restart Visual Studio Code after modifying the `settings.json` or other configuration files to ensure changes take effect.