https://github.com/sepatel/maven-scm-version-plugin

Automatically alter version numbers of branched code to include branch name for simplified parrallel development.
https://github.com/sepatel/maven-scm-version-plugin

Last synced: about 1 month ago
JSON representation

Automatically alter version numbers of branched code to include branch name for simplified parrallel development.

• Host: GitHub
• URL: https://github.com/sepatel/maven-scm-version-plugin
• Owner: sepatel
• License: apache-2.0
• Created: 2012-03-20T14:16:48.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2015-11-22T22:19:18.000Z (about 9 years ago)
• Last Synced: 2023-12-17T17:05:17.492Z (about 1 year ago)
• Language: Java
• Homepage:
• Size: 27.3 KB
• Stars: 2
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
Purpose

-------

The purpose of this plugin is to allow a dynamic version of the project

being worked on if and only if it is a SNAPSHOT. The reason one might

desire this may be a use case such as you branch your code base and

want the artifacts to automatically be versioned to reflect the branch

name instead of the original version number.

This specific case is beneficial to development for many reasons some

of which include allowing multiple parallel development initiatives in

a group without manual alteration of version numbers. Thus any system

for continuous build would not stomp upon one another giving the most

recent committer the winning artifact for use downstream by others.

It would also make merges back into the main codebase easier in that it

would not cause for conflicts on the pom.xml file itself simply because

the version number was manually changed to resolve the above mentioned

issue.

There are another reasons for the version numbers to be dynamically set

at build time rather then via a predetermined value and this plugin is

to help work around the lack of said capability within the core maven

capabilities.

Quick Start Guide

-----------------

A typical use case for utilizing these plugins in the intended fashion

is to put in the following snippet into the parent pom of the project.

    

       

       ${project.artifactId}-${scmVersion}

       

         

           org.inigma.maven

           maven-scm-version-plugin

           1.2

           

             

               

                 gitVersion

                 pomInstall

                 pomDeploy