[
https://jira.codehaus.org/browse/MBUILDNUM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283215#comment-283215
]
Peter Boudreau commented on MBUILDNUM-11:
-----------------------------------------
I have been setting up a project to use the buildNumber plugin, and have
observed that it seems to be extracting its build number information from *svn
info*, rather than from *svnversion*.
For an example of the distinction between the two, if I have checked out
Subversion Revision 124 from my repository and then modified a file, *svn info*
will tell me my revision is *124*, whereas *svnversion* will tell me its
*124M*. For my purposes, it is very important to know when Im building with a
pure revision versus a modified one.
Is there any way to access this *svnversion* capability thru the existing pom
attributes for the buildNumber plugin? If not, could such a switch be made
available?
Thank you for any help you can provide!
Cheers,
Peter
> svnversion is better than svn -info for build numbers.
> ------------------------------------------------------
>
> Key: MBUILDNUM-11
> URL: https://jira.codehaus.org/browse/MBUILDNUM-11
> Project: Mojo Build Number Maven Plugin
> Issue Type: Improvement
> Environment: Any subversion
> Reporter: James R. Collings
>
> "svn --info" isn't the proper subversion tool for retrieving version info of
> local copy.
> See this thread:
> http://tinyurl.com/yh4mzf7
> The point is that I might be using a generated artifact and not be quite
> certain of the version and/or the status of that version. 'svnversion' will
> handle this while svn --info does not.
--
This message is automatically generated by JIRA.
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
