[
https://issues.apache.org/jira/browse/LUCENE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125900#comment-14125900
]
Uwe Schindler commented on LUCENE-4073:
---------------------------------------
I will fix this soon.
> Lucene puts output of svnversion into a property even if svnversion failed
> --------------------------------------------------------------------------
>
> Key: LUCENE-4073
> URL: https://issues.apache.org/jira/browse/LUCENE-4073
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Environment: Windows 7 x64, Cygwin for tools like svn
> Reporter: Trejkaz
>
> We had a build issue today where Lucene was running svnversion which was
> failing (the reason for the failure itself is not particularly important.)
> As a result, the error text output of running the command ended up in the
> svnversion property. The build later attempted to insert this into
> MANIFEST.MF which resulted in an invalid manifest file, causing the build to
> fail.
> A related observation is that even if it works, the svnversion would be the
> version of our own repository, so the usefulness of it in the context of
> Lucene's version number is questionable anyway. It would be nice if the build
> could get the svn version number only if it was checked out from Lucene trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
