[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627108#action_12627108
]
Hoss Man commented on SOLR-684:
-------------------------------
bq. When you get something like 690356:690357M it's highly unlikely that this
will help you to uniquely identify the "revision" as a whole or recreate it,
which I think is the point of including it in the manifest.
True: but it will tell you that you *can't* recreate it purely from the
repository. having the svnversion info is just an added bit of security
blanket for people who later want a starting point to understand where the
release came from -- when it's a single number, you have a good starting point.
when it's mixed you have an ambiguous starting point, and when it's got an "M"
all bets are off.
> 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.
