[
http://jira.codehaus.org/browse/MBUILDNUM-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Huber updated MBUILDNUM-12:
-----------------------------------
Attachment: CreateMojo.patch
I have done a small patch.
Usage:
The following configuration:
{code:xml}
<format>R{0}-B{1,number}</format><items><item>scmRevision</item><item>buildNumber0</item></items>
{code}
will produce following ${buildNumber} (for SCM Rev 6 and local Buildrevision 3):
{noformat}
R6-B3
{noformat}
> There is no way how to get SVN revision into formatted buildNumber
> ------------------------------------------------------------------
>
> Key: MBUILDNUM-12
> URL: http://jira.codehaus.org/browse/MBUILDNUM-12
> Project: Mojo Build Number Maven Plugin
> Issue Type: Improvement
> Environment: Windows 32-bit
> Reporter: Roman Zenka
> Priority: Minor
> Attachments: CreateMojo.patch
>
>
> The buildNumber understand two special kinds of items - timestamp and
> buildNumber???. The latter will produce a special property file and will
> start incrementing the buildNumber??? property.
> I spend quite some time to figure out the following:
> 1) buildNumber\*d in documentation is a regular expression, not a command!
> These guys got it wrong:
> http://www.packtpub.com/article/useful-maven-plugins-part1
> 2) Using e.g. buildNumber1 will enforce new numbering, will NOT use the SVN
> revision, even if available
> 3) There is currently no way to use <format> and <info> to get the SVN
> revision
> This needs clarifications in the documentation + possibly introduction of a
> new, special variable (maybe called scmRevisionNumber) ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
