How to Install and Uninstall httpcomponents-core.noarch Package on Amazon Linux 2

Last updated: May 15,2024

1. Install "httpcomponents-core.noarch" package

This is a short guide on how to install httpcomponents-core.noarch on Amazon Linux 2


    
        
            $
        

        
            
                sudo yum makecache
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum install
            
                        
                httpcomponents-core.noarch
            
                    
    
    Copied

2. Uninstall "httpcomponents-core.noarch" package

Here is a brief guide to show you how to uninstall httpcomponents-core.noarch on Amazon Linux 2:


    
        
            $
        

        
            
                sudo yum remove 
            
                        
                httpcomponents-core.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum autoremove
            
                    
    
    Copied

3. Information about the httpcomponents-core.noarch package on Amazon Linux 2

Loaded plugins: ovl, priorities
Available Packages
Name : httpcomponents-core
Arch : noarch
Version : 4.2.4
Release : 6.amzn2
Size : 465 k
Repo : amzn2-core/2/x86_64
Summary : Set of low level Java HTTP transport components for HTTP services
URL : http://hc.apache.org/
License : ASL 2.0 and CC-BY
Description : HttpCore is a set of low level HTTP transport components that can
: be used to build custom client and server side HTTP services with
: a minimal footprint. HttpCore supports two I/O models: blocking
: I/O model based on the classic Java I/O and non-blocking, event
: driven I/O model based on Java NIO.
:
: The blocking I/O model may be more appropriate for data intensive,
: low latency scenarios, whereas the non-blocking model may be more
: appropriate for high latency scenarios where raw data throughput
: is less important than the ability to handle thousands of
: simultaneous HTTP connections in a resource efficient manner.