|
||||||||
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)
The drawback with using a sequential build number is that it won't uniquely identify the build from a DVCS. There might be several versions of the repository with the same number of commits.
See
Understanding Mercurial - 3. Revisions, changesets, heads, and tip