Mojo Build Number Maven Plugin

Generate buildnumber as a commit sequence number for Git

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

New feature is offered to compute Subversion-style build numbers for Git repositories.

Build number increasing sequence is desired e.g. for correct updates recognition of Netbeans modules.

Proposed patch providing this functionality is attached.

When new parameter gitCountCommits is set to true, patched info method in CreateMojo counts all existing commits in the repository and assigns the result as new build number. In addition, when useLastCommittedRevision is set to true, HEAD revision of the working directory is found and commit sequence number of it is found and assigned as build number instead.

The patch works fine with my projects - when Subversion repository was converted to Git, plugin created identical build numbers for all modules.

Issue Links

is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MBUILDNUM-104 Sequential buildnumber with git SCM based on number of commits

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Frantisek Mantlik added a comment -

Updated patch uses git log instead of git whatchanged. This gives better results on some edge situations.

Show
Frantisek Mantlik added a comment - Updated patch uses git log instead of git whatchanged. This gives better results on some edge situations.
Hide
Permalink
Tomáš Procházka added a comment -

I vote for integrate this patch. I use this plugin together with com.google.code.maven-replacer-plugin to auto generate versionCode in Android manifest file and this allow use it also on GIT.

Show
Tomáš Procházka added a comment - I vote for integrate this patch. I use this plugin together with com.google.code.maven-replacer-plugin to auto generate versionCode in Android manifest file and this allow use it also on GIT.
Hide
Permalink
Tomáš Procházka added a comment -

Is any chance that this will be integrated? Or exist any other solution how to get unique incremental number from GIT for tagging build number?

Show
Tomáš Procházka added a comment - Is any chance that this will be integrated? Or exist any other solution how to get unique incremental number from GIT for tagging build number?
Hide
Permalink
Tomáš Procházka added a comment -

I investigated it more detailed and problem of this solution is that it completely replace original commit hash which identify build. I think that much better will be add additional variable and keep buildNumber intact.

Show
Tomáš Procházka added a comment - I investigated it more detailed and problem of this solution is that it completely replace original commit hash which identify build. I think that much better will be add additional variable and keep buildNumber intact.
Hide
Permalink
Frantisek Mantlik added a comment -

Maybe it would be better to keep buildnumber the sequence build number as proposed in the proposed patch and introduce an additional variable for Git commit hash?

It should be noticed that the build sequence number replaces Git hash when gitCountCommits parameter is set to true (default is false, i.e. current behavior).

In either case I would appreciate very much any implementation of commit sequence number to be incorporated into the official release.

Show
Frantisek Mantlik added a comment - Maybe it would be better to keep buildnumber the sequence build number as proposed in the proposed patch and introduce an additional variable for Git commit hash? It should be noticed that the build sequence number replaces Git hash when gitCountCommits parameter is set to true (default is false, i.e. current behavior). In either case I would appreciate very much any implementation of commit sequence number to be incorporated into the official release.
Hide
Permalink
Jörg von Frantzius added a comment - - edited

As discussed in duplicating issue MBUILDNUM-104 , it may make sense to combine the commit count with a short hash as e.g. git describe already does.

Build numbers within the same branch would remain orderable, while build numbers from different branches would at least be guaranteed to be different.

Another example of update recognition based on build number sequences is the Open Source Magnolia CMS, where it was possible to simply suffix a module version number with the SVN revision in order to get a module update recognized.

Show
Jörg von Frantzius added a comment - - edited As discussed in duplicating issue MBUILDNUM-104 , it may make sense to combine the commit count with a short hash as e.g. git describe already does. Build numbers within the same branch would remain orderable, while build numbers from different branches would at least be guaranteed to be different. Another example of update recognition based on build number sequences is the Open Source Magnolia CMS , where it was possible to simply suffix a module version number with the SVN revision in order to get a module update recognized.

People

  • Assignee:
    Unassigned
    Reporter:
    Frantisek Mantlik
Vote (2)
Watch (3)

Dates

  • Created:
    Updated: