How to Install and Uninstall jackson-module-blackbird Package on openSUSE Leap

Last updated: July 03,2024

1. Install "jackson-module-blackbird" package

Please follow the step by step instructions below to install jackson-module-blackbird on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                jackson-module-blackbird
            
                    
    
    Copied

2. Uninstall "jackson-module-blackbird" package

This guide let you learn how to uninstall jackson-module-blackbird on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                jackson-module-blackbird
            
                    
    
    Copied

3. Information about the jackson-module-blackbird package on openSUSE Leap

Information for package jackson-module-blackbird:
-------------------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : jackson-module-blackbird
Version : 2.15.2-150200.5.6.2
Arch : noarch
Vendor : SUSE LLC
Installed Size : 73.5 KiB
Installed : No
Status : not installed
Source package : jackson-modules-base-2.15.2-150200.5.6.2.src
Upstream URL : https://github.com/FasterXML/jackson-modules-base
Summary : Jackson module that uses LambdaMetafactory based code generation to replace reflection calls.
Description :
The LambdaMetafactory introduces a standard Java API for dynamically instantiating function objects.
The current OpenJDK implementation generates anonymous classes in a somewhat similar fashion to the
classic Afterburner. While the metafactory cannot generate comparably specialized implementations,
we can write needed adapters as simple Java code and use the metafactory to create distinct call
sites for every needed access path. This should allow each accessor to have a monomorphic call
profile and easily inline for maximum performance.