[
https://issues.apache.org/jira/browse/LUCENE-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041591#comment-13041591
]
Robert Muir commented on LUCENE-3165:
-------------------------------------
{quote}
One comment, but I'm not a native English speaker - is it correct to say "AN
svn checkout ..." instead of "A svn checkout ..."?
{quote}
Its confusing really, when to use 'a' or 'an' depends actually upon whether the
word starts with a vowel sound instead of a vowel letter. So you would say
'This test failed in an hourly build yesterday', but you would say 'I bought a
horse yesterday'
http://en.wikipedia.org/wiki/A_and_an#Indefinite_article
> prepare-release fails if run from source package
> ------------------------------------------------
>
> Key: LUCENE-3165
> URL: https://issues.apache.org/jira/browse/LUCENE-3165
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Reporter: Shai Erera
> Assignee: Robert Muir
> Priority: Blocker
> Fix For: 3.3, 4.0
>
> Attachments: LUCENE-3165.patch
>
>
> While checking 3.2 RC2 artifacts, I ran "ant prepare-release" and it failed
> because "get-svn-info" failed (since this is not a svn checkout). This makes
> sense indeed, but still annoying, so question is how to overcome it? It
> attempts to execute "svn info" as part of "package-tgz-src". When you run the
> latter to prepare the release, you want it to fail if "svn" does not exist,
> however in the source package there's no '.svn' so it cannot succeed.
> On the other hand, nobody should "prepare a release" from the source package,
> so perhaps the failure is ok, and we should disable the Ant target?
> I don't know how to solve it yet, so I'm marking it as a Blocker for 3.3, so
> that we at least revisit it before then.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
