|
||||||||
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-104) Sequential buil... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... Rickard von Essen (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... Rickard von Essen (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... JIRA
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-104) Sequential... Baptiste Mathus (JIRA)
One approach could be to not replace the SHA as buildnumber by default, but to optionally be able to use it (if the user knows what he is doing).
Alternatively, it could be a compromise to add the SHA as a suffix to the number of commits, somewhat similar to git describe. The resulting build numbers so would be unique across repositories, and yet be orderable for the same repository.