lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7543) Make changes-to-html target an offline operation
Date Wed, 25 Jan 2017 18:08:27 GMT


ASF subversion and git services commented on LUCENE-7543:

Commit 14812fa1bcbb7fcf1d1e289f0633fa8ffc9f7dc6 in lucene-solr's branch refs/heads/branch_6_4
from [~steve_rowe]
[;h=14812fa ]

LUCENE-7543: Treat product name passed into case-insensitively, and validate
that the product name is either 'lucene' or 'solr'

> Make changes-to-html target an offline operation
> ------------------------------------------------
>                 Key: LUCENE-7543
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>             Fix For: master (7.0), 6.0.2, 6.1.1, 5.6, 5.5.4, 6.2.2, 6.4, 6.3.1
>         Attachments: LUCENE-7543-drop-XML-Simple.patch, LUCENE-7543.patch, LUCENE-7543.patch,
> Currently changes-to-html pulls release dates from JIRA, and so fails when JIRA is inaccessible
(e.g. from behind a firewall).
> SOLR-9711 advocates adding a build sysprop to ignore JIRA connection failures, but I'd
rather make the operation always offline.
> In an offline discussion, [~hossman] advocated moving Lucene's and Solr's {{doap.rdf}}
files, which contain all of the release dates that the changes-to-html now pulls from JIRA,
from the CMS Subversion repository (downloadable from the website at
and to the Lucene/Solr git repository. If we did that,
then the process could be entirely offline if release dates were taken from the local {{doap.rdf}}
files instead of downloaded from JIRA.

This message was sent by Atlassian JIRA

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

View raw message