How to Install and Uninstall jakarta-commons-discovery Package on openSUSE Leap
Last updated: December 25,2024
1. Install "jakarta-commons-discovery" package
Learn how to install jakarta-commons-discovery on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
jakarta-commons-discovery
Copied
2. Uninstall "jakarta-commons-discovery" package
This guide let you learn how to uninstall jakarta-commons-discovery on openSUSE Leap:
$
sudo zypper remove
jakarta-commons-discovery
Copied
3. Information about the jakarta-commons-discovery package on openSUSE Leap
Information for package jakarta-commons-discovery:
--------------------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : jakarta-commons-discovery
Version : 0.5-150000.4.11.1
Arch : noarch
Vendor : SUSE LLC
Installed Size : 99.4 KiB
Installed : No
Status : not installed
Source package : jakarta-commons-discovery-0.5-150000.4.11.1.src
Upstream URL : http://jakarta.apache.org/commons/discovery.html
Summary : Jakarta Commons Discovery
Description :
The Discovery component is about discovering, or finding,
implementations for pluggable interfaces. Pluggable interfaces are
specified with the intent that multiple implementations are, or will
be, available to provide the service described by the interface.
Discovery provides facilities for finding and instantiating classes and
for lifecycle management of singleton (factory) classes.
--------------------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : jakarta-commons-discovery
Version : 0.5-150000.4.11.1
Arch : noarch
Vendor : SUSE LLC
Installed Size : 99.4 KiB
Installed : No
Status : not installed
Source package : jakarta-commons-discovery-0.5-150000.4.11.1.src
Upstream URL : http://jakarta.apache.org/commons/discovery.html
Summary : Jakarta Commons Discovery
Description :
The Discovery component is about discovering, or finding,
implementations for pluggable interfaces. Pluggable interfaces are
specified with the intent that multiple implementations are, or will
be, available to provide the service described by the interface.
Discovery provides facilities for finding and instantiating classes and
for lifecycle management of singleton (factory) classes.