lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5104) needs fixed
Date Fri, 12 Jul 2013 18:23:48 GMT


Hoss Man commented on LUCENE-5104:

bq. One thing I noticed: your $usage includes "-V" but doesn't mention "-details" - I'm guessing
you renamed the option but didn't change the $usage?

Good eye ... yeah, originally i named "-details" "-Verbose" but the way we are using GetOpt
it does case insensitive short form args, so trying to use "-v 4.3.1" would error that -v
was too vague (it didn't know if you wanted -verbose or -version) and i was too lazy to completely
revamp the arg parsing to use something more sophisticated.

bq. The way I've used that script, the question has been: Can I announce that the release
is available? This is answered when all parts of the release are downloadable ...

I hear you, and i have some ideas of how to make it work better for what you're describing,
but it means gutting most of how works now, so i split that off into LUCENE-5108

> needs fixed
> ---------------------------
>                 Key: LUCENE-5104
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Hoss Man
>             Fix For: 4.4
>         Attachments: LUCENE-5104.patch, LUCENE-5104.patch
> i just noticed that is setup to look for the KEYS file in the release
dir on each mirror -- Infra (wisely) tweaked the way mirroring happens recently to ensure
that KEYS files are *not* mirrored anymore (presumably to help catch bad links advising people
to download untrusted KEYS files)
> we're going to need to updated to look for something else in each release
dir ... changes/Changes.html perhaps?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message