[
http://jira.codehaus.org/browse/MOJO-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198067#action_198067
]
Baptiste MATHUS commented on MOJO-1452:
---------------------------------------
I agree with this request.
Another use case would be a non versionned project. 'svn info' will throw an
exception. svnversion will just output 'exported' as the code isn't versioned.
The thing is: after a quick look in the buildnumber code, it seems like the
corresponding code isn't in buildnumber, but in one of the scm-svn provider
api. But if an interface to svnversion if already offered by this API, the
evolution should be feasible.
Cheers
> svnversion is better than svn -info for build numbers.
> ------------------------------------------------------
>
> Key: MOJO-1452
> URL: http://jira.codehaus.org/browse/MOJO-1452
> Project: Mojo
> Issue Type: Improvement
> Components: _Plugin Submission
> Affects Versions: buildnumber-maven-plugin-1.0-beta-3
> 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.
-
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
