How to Install and Uninstall apache-commons-logging.noarch Package on Fedora 39

Last updated: January 07,2025

1. Install "apache-commons-logging.noarch" package

This tutorial shows how to install apache-commons-logging.noarch on Fedora 39


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                apache-commons-logging.noarch
            
                    
    
    Copied

2. Uninstall "apache-commons-logging.noarch" package

Please follow the guidelines below to uninstall apache-commons-logging.noarch on Fedora 39:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                apache-commons-logging.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the apache-commons-logging.noarch package on Fedora 39

Last metadata expiration check: 4:47:08 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : apache-commons-logging
Version : 1.2
Release : 34.fc39
Architecture : noarch
Size : 78 k
Source : apache-commons-logging-1.2-34.fc39.src.rpm
Repository : fedora
Summary : Apache Commons Logging
URL : https://commons.apache.org/proper/commons-logging/
License : Apache-2.0
Description : The commons-logging package provides a simple, component oriented
: interface (org.apache.commons.logging.Log) together with wrappers for
: logging systems. The user can choose at runtime which system they want
: to use. In addition, a small number of basic implementations are
: provided to allow users to use the package standalone.
: commons-logging was heavily influenced by Avalon's Logkit and Log4J. The
: commons-logging abstraction is meant to minimize the differences between
: the two, and to allow a developer to not tie himself to a particular
: logging implementation.