[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627097#action_12627097
]
Hoss Man commented on SOLR-684:
-------------------------------
bq. In case this ever needs to be done with pure "svn":
I strongly recommend people don't do that ... or at least, don't assume it's
equivalent.
svnversion is automatically recursive, and aware of both mixed version trees
and local modifications, so you can get output like this...
{code}
[EMAIL PROTECTED]:~/lucene/solr$ svnversion
690356:690357M
{code}
...when the revs of your files vary between 690356 and 690357 and some files
deep in your tree are locally modified.
attempting to get the same information out of "pure svn" would require shell
scripting the likes of which would likely drive you insane.
> Hudson builds do not have the SVN revision because svnversion is not available
> ------------------------------------------------------------------------------
>
> Key: SOLR-684
> URL: https://issues.apache.org/jira/browse/SOLR-684
> Project: Solr
> Issue Type: Task
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 1.3
>
>
> The build file tries to run svnversion when generating the jar manifest to
> include the revision number. This fails in Hudson however as the svnversion
> executable is not available.
> This could be addressed by installing svnversion on the build machine or
> using alternative means of determining the revision number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
