|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MBUILDNUM-93) Generate buildnumber as a commit seq... JIRA
- [mojo-dev] [jira] (MBUILDNUM-93) Generate buildnumber as a commi... JIRA
- [mojo-dev] [jira] (MBUILDNUM-93) Generate buildnumber as a commi... JIRA
- [mojo-dev] [jira] (MBUILDNUM-93) Generate buildnumber as a commi... JIRA
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.