[LUCENE-7543] Make changes-to-html target an offline operation

• Type: Task
• Status: Reopened
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.5.4, 5.6, 6.0.2, 6.1.1, 6.2.2, 6.3.1, 6.4, 6.4.1, 6.5, 7.0
• Lucene Fields: New
• Assignee: Steven Rowe
• Reporter: Steven Rowe
• Created: 07/Nov/16 18:20
• Updated: 02/Sep/24 07:57
• Resolved: 25/Jan/17 18:15

Description

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, Chris M. Hostetter 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 http://lucene.apache.org/core/doap.rdf and http://lucene.apache.org/solr/doap.rdf) 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.

Issue Links

• is related to: SOLR-9711 Build parameter to silence Changes.html generation error if SOLR Jira is not accessible