search
  • Sign In
  • Sign Up
Password reset successful

Follow the proiects vou are interested in andi aet the latestnews about them taster

Table of Contents
Understand common misunderstandings about OpenJDK uninstallation
Identify installed OpenJDK version
Precisely uninstall unwanted OpenJDK versions
Multi-version compatibility and management strategies
Summary and best practices
Home Java javaTutorial Ubuntu system OpenJDK multi-version management and uninstallation tutorial

Ubuntu system OpenJDK multi-version management and uninstallation tutorial

Dec 31, 2025 am 08:57 AM

Ubuntu system OpenJDK multi-version management and uninstallation tutorial

In response to common confusions about the installation and uninstallation of multiple versions of OpenJDK on Ubuntu systems, this tutorial will provide detailed guidance on how to correctly identify, manage and safely remove unnecessary OpenJDK versions. This article will correct common mistakes in using wildcard uninstallation, and provide steps for accurate uninstallation using the APT package manager. It will also discuss the compatibility between different Java versions to help users effectively maintain the development environment.

Understand common misunderstandings about OpenJDK uninstallation

In a Linux environment, especially for first-time users, a common problem often occurs when trying to uninstall OpenJDK: incorrectly using wildcards (such as openjdk*) in combination with package management commands. When you enter sudo apt remove openjdk* on the command line, the shell will try to expand openjdk* to all file or directory names starting with openjdk in the current directory before executing the apt command. If such files exist in the current directory, the apt command will receive these file/directory names instead of the expected package names, causing the uninstallation to fail or report an error.

Error example:

 sudo apt remove openjdk*
# Assume that the current directory has a file named "openjdk-doc.txt",
# Then the actual execution may be: sudo apt remove openjdk-doc.txt
# This is obviously not a valid package name, so an error will be reported.

Core takeaway: When using package management tools such as apt or dpkg, you must specify the specific package name instead of relying on the shell's wildcard expansion.

Identify installed OpenJDK version

Before performing any uninstallation operations, you first need to know exactly which versions of OpenJDK are installed on your system. This can be achieved in a number of ways:

  1. List all installed OpenJDK-related packages: Use the dpkg command to list all installed software packages and filter out OpenJDK-related packages through grep.

     dpkg -l | grep openjdk

    Or use the apt list command:

     apt list --installed | grep openjdk

    These commands will output specific package names such as openjdk-11-jdk, openjdk-8-jre, etc. These are the names that need to be used when uninstalling.

  2. Check the current default Java version: Although this does not directly display all installed versions, it can help you understand which Java environment the current system is using.

     java-version

Precisely uninstall unwanted OpenJDK versions

Once the OpenJDK package name to be uninstalled is determined, you can use the apt remove or apt purge command to uninstall it accurately.

  1. Uninstalling a specific OpenJDK version (preserving configuration files): Using the apt remove command will uninstall the package but may preserve its configuration files.

     sudo apt remove <package_name_1> <package_name_2> ...</package_name_2></package_name_1>

    Example: If you want to uninstall the JRE and JDK of OpenJDK 8:

     sudo apt remove openjdk-8-jre openjdk-8-jdk
  2. Completely uninstall a specific OpenJDK version (delete all configuration files): Using the apt purge command will completely remove the package and all configuration files for a more thorough cleanup. This command is recommended for versions of OpenJDK that are no longer needed.

     sudo apt purge <package_name_1> <package_name_2> ...</package_name_2></package_name_1>

    Example: Completely uninstall the JRE and JDK of OpenJDK 8:

     sudo apt purge openjdk-8-jre openjdk-8-jdk
  3. Clean up residual dependencies: After uninstalling certain software packages, some dependency packages that are no longer needed may be left behind. You can use the autoremove command to clean it up.

     sudo apt autoremove

Multi-version compatibility and management strategies

When dealing with multiple Java versions, it is crucial to understand their compatibility features.

  • Backward compatibility: Modern Java versions generally have good backward compatibility. For example, Java 17 is generally able to compile and run code written for Java 8. This means that if you have a newer Java version installed (such as Java 17), you may not need to keep the older Java 8 version unless there are very specific compatibility needs or legacy projects that mandate it.

  • Multi-version coexistence: The Ubuntu system allows the installation of multiple OpenJDK versions. Through the update-alternatives tool, you can manage the Java version used by the system by default.

    • List all Java options:
       sudo update-alternatives --config java
      sudo update-alternatives --config javac
    • Select the default version: After executing the above command, the system will list all installed Java versions and prompt you to select one as the default version.

Therefore, when deciding which versions to uninstall, you can prioritize keeping the latest and fully functional OpenJDK version, and remove older versions that are no longer needed based on project needs.

Summary and best practices

To effectively manage OpenJDK versions on Ubuntu, follow these best practices:

  1. Avoid using wildcards for uninstallation: Always use specific package names for apt remove or apt purge operations to prevent errors caused by shell expansion.
  2. Identify the installed version in advance: Before uninstalling, use the dpkg -l | grep openjdk or apt list --installed | grep openjdk command to confirm the precise package name to be uninstalled.
  3. Choose an appropriate uninstall command: For a thorough cleanup, sudo apt purge is recommended.
  4. Consider version compatibility: Given Java's backward compatibility, you can usually keep the latest OpenJDK version and remove older versions unless there are specific project dependencies.
  5. Regular cleaning: After uninstalling, run sudo apt autoremove to clean up dependent packages that are no longer needed to keep the system clean.

By following these steps and recommendations, you can effectively manage your OpenJDK environment on your Ubuntu system, avoid unnecessary confusion, and ensure a stable and efficient development environment.

The above is the detailed content of Ubuntu system OpenJDK multi-version management and uninstallation tutorial. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undress AI Tool

Undress AI Tool

Undress images for free

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

ArtGPT

ArtGPT

AI image generator for creative art from text prompts.

Stock Market GPT

Stock Market GPT

AI powered investment research for smarter decisions

Popular tool

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

How to configure Spark distributed computing environment in Java_Java big data processing How to configure Spark distributed computing environment in Java_Java big data processing Mar 09, 2026 pm 08:45 PM

Spark cannot run in local mode, ClassNotFoundException: org.apache.spark.sql.SparkSession. This is the most common first step of getting stuck: even the dependencies are not correct. Only spark-core_2.12 is written in Maven, but spark-sql_2.12 is not added. SparkSession crashes as soon as it is built. The Scala version must strictly match the official Spark compiled version - Spark3.4.x uses Scala2.12 by default. If you use spark-sqljar of 2.13, the class loader cannot directly find the main class. Practical advice: Go to mvnre

How to safely map user-entered weekday string to integer value and implement date offset operation in Java How to safely map user-entered weekday string to integer value and implement date offset operation in Java Mar 09, 2026 pm 09:43 PM

This article introduces a concise and maintainable way to map the weekday string (such as "Monday") to the corresponding serial number (1-7), and use the modulo operation to realize the forward and backward offset of any number of days (such as Monday plus 4 days to get Friday), avoiding lengthy if chains and hard-coded logic.

How to generate a list of duplicate elements using Java's Collections.nCopies_Initialization tips How to generate a list of duplicate elements using Java's Collections.nCopies_Initialization tips Mar 06, 2026 am 06:24 AM

Collections.nCopies returns an immutable view. Calling add/remove will throw UnsupportedOperationException; it needs to be wrapped with newArrayList() to modify it, and it is disabled for mutable objects.

What is exception masking (Suppressed Exceptions) in Java_Multiple resource shutdown exception handling What is exception masking (Suppressed Exceptions) in Java_Multiple resource shutdown exception handling Mar 10, 2026 pm 06:57 PM

What is SuppressedException: It is not "swallowed", but actively archived by the JVM. SuppressedException is not an exception loss, but the JVM quietly attaches the secondary exception to the main exception under the premise that "only one exception must be thrown" for you to verify afterwards. It is automatically triggered by the JVM in only two scenarios: one is that the resource closure in try-with-resources fails, and the other is that you manually call addSuppressed() in finally. The key difference is: the former is fully automatic and safe; the latter requires you to keep it to yourself, and it can be written as shadowing if you are not careful. try-

How to use Homebrew to install Java on Mac_A must-have Java tool chain for developers How to use Homebrew to install Java on Mac_A must-have Java tool chain for developers Mar 09, 2026 pm 09:48 PM

Homebrew installs the latest stable version of openjdk (such as JDK22) by default, not the LTS version; you need to explicitly execute brewinstallopenjdk@17 or brewinstallopenjdk@21 to install the LTS version, and manually configure PATH and JAVA_HOME to be correctly recognized by the system and IDE.

How to correctly implement runtime file writing in Java applications (avoiding JAR internal write failures) How to correctly implement runtime file writing in Java applications (avoiding JAR internal write failures) Mar 09, 2026 pm 07:57 PM

After a Java application is packaged as a JAR, data cannot be written directly to the resources in the JAR package (such as test.txt) because the JAR is essentially a read-only ZIP archive; the correct approach is to write variable data to an external path (such as a user directory, a temporary directory, or a configuration-specified path).

What is the underlying principle of array expansion in Java_Java memory dynamic adjustment analysis What is the underlying principle of array expansion in Java_Java memory dynamic adjustment analysis Mar 09, 2026 pm 09:45 PM

ArrayList.add() triggers expansion because grow() is called when size is equal to elementData.length. The first add allocates 10 capacity, and subsequent expansion is 1.5 times and not less than the minimum requirement, relying on delayed initialization and System.arraycopy optimization.

How to safely read a line of integer input in Java and avoid Scanner blocking How to safely read a line of integer input in Java and avoid Scanner blocking Mar 06, 2026 am 06:21 AM

This article introduces typical blocking problems when using Scanner to read multiple integers in a single line. It points out that hasNextInt() will wait indefinitely when there is no subsequent input, and recommends a safe alternative with nextLine() string splitting as the core.

Related articles