How to Install and Uninstall libcommons-launcher-java Package on Ubuntu 16.04 LTS (Xenial Xerus)

Last updated: November 26,2024

1. Install "libcommons-launcher-java" package

This guide covers the steps necessary to install libcommons-launcher-java on Ubuntu 16.04 LTS (Xenial Xerus)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                libcommons-launcher-java
            
                    
    
    Copied

2. Uninstall "libcommons-launcher-java" package

Please follow the instructions below to uninstall libcommons-launcher-java on Ubuntu 16.04 LTS (Xenial Xerus):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                libcommons-launcher-java
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the libcommons-launcher-java package on Ubuntu 16.04 LTS (Xenial Xerus)

Package: libcommons-launcher-java
Priority: optional
Section: universe/libs
Installed-Size: 664
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Java Maintainers
Architecture: all
Version: 1.1-8
Depends: libcommons-collections3-java, libcommons-logging-java
Filename: pool/universe/libc/libcommons-launcher-java/libcommons-launcher-java_1.1-8_all.deb
Size: 148100
MD5sum: f2fdbde2c5a746226c36bc3da8a9abbf
SHA1: 89cd0bca4e15dbcbc1e538a774f07b045cfc388f
SHA256: f78860f8105b8186e5b430464cd4d317a37c200e1e3c491cf291982c573edb3e
Description-en: Apache Commons Launcher - Cross platform Java application launcher
Commons-launcher eliminates the need for a batch or shell script to
launch a Java class. Some situations where elimination of a batch or
shell script may be desirable are:
.
* You want to avoid having to determining where certain application
paths are e.g. your application's home directory, etc. Determining this
dynamically in a Windows batch scripts is very tricky on some versions
of Windows or when softlinks are used on Unix platforms.
.
* You want to avoid having to handle native file and path separators
or native path quoting issues.
.
* You need to enforce certain system properties
e.g. java.endorsed.dirs when running with JDK 1.4.
.
* You want to allow users to pass in custom JVM arguments or system
properties without having to parse and reorder arguments in your
script. This can be tricky and/or messy in batch and shell scripts.
.
* You want to bootstrap system properties from a configuration file
instead hard-coding them in your batch and shell scripts.
.
* You want to provide localized error messages which is very tricky
to do in batch and shell scripts.
Description-md5: 96614979f2ef4bd0ac27717cbd53736c
Homepage: http://commons.apache.org/launcher/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu