How to Install and Uninstall buildnumber-maven-plugin Package on openSuSE Tumbleweed

Last updated: November 07,2024

1. Install "buildnumber-maven-plugin" package

This is a short guide on how to install buildnumber-maven-plugin on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                buildnumber-maven-plugin
            
                    
    
    Copied

2. Uninstall "buildnumber-maven-plugin" package

This tutorial shows how to uninstall buildnumber-maven-plugin on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                buildnumber-maven-plugin
            
                    
    
    Copied

3. Information about the buildnumber-maven-plugin package on openSuSE Tumbleweed

Information for package buildnumber-maven-plugin:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : buildnumber-maven-plugin
Version : 1.3-3.3
Arch : noarch
Vendor : openSUSE
Installed Size : 60.9 KiB
Installed : No
Status : not installed
Source package : buildnumber-maven-plugin-1.3-3.3.src
Upstream URL : http://svn.codehaus.org/mojo/tags/buildnumber-maven-plugin-1.3
Summary : Build Number Maven Plugin
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.