How to Install and Uninstall buildnumber-maven-plugin.noarch Package on Amazon Linux 2

Last updated: November 25,2024

1. Install "buildnumber-maven-plugin.noarch" package

This tutorial shows how to install buildnumber-maven-plugin.noarch on Amazon Linux 2


    
        
            $
        

        
            
                sudo yum makecache
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum install
            
                        
                buildnumber-maven-plugin.noarch
            
                    
    
    Copied

2. Uninstall "buildnumber-maven-plugin.noarch" package

In this section, we are going to explain the necessary steps to uninstall buildnumber-maven-plugin.noarch on Amazon Linux 2:


    
        
            $
        

        
            
                sudo yum remove 
            
                        
                buildnumber-maven-plugin.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum autoremove
            
                    
    
    Copied

3. Information about the buildnumber-maven-plugin.noarch package on Amazon Linux 2

Loaded plugins: ovl, priorities
Available Packages
Name : buildnumber-maven-plugin
Arch : noarch
Version : 1.2
Release : 7.amzn2
Size : 42 k
Repo : amzn2-core/2/x86_64
Summary : Build Number Maven Plugin
URL : http://svn.codehaus.org/mojo/tags/buildnumber-maven-plugin-1.2
License : MIT and ASL 2.0
Description : This mojo is designed to get a unique build number for each time
: you build your project. So while your version may remain constant
: at 1.0-SNAPSHOT for many iterations until release, you will have a
: build number that can uniquely identify each build during that
: time. The build number is obtained from scm, and in particular, at
: this time, from svn. You can then place that build number in
: metadata, which can be accessed from your app, if desired.
:
: The mojo also has a couple of extra functions to ensure you get
: the proper build number. First, your local repository is checked
: to make sure it is up to date. Second, your local repository is
: automatically updated, so that you get the latest build number.
: Both these functions can be suppressed, if desired.
:
: Optionally, you can configure this mojo to produce a revision
: based on a timestamp, or on a sequence, without requiring any
: interaction with an SCM system. Note that currently, the only
: supported SCM is subversion.