You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/11/21 23:31:58 UTC
[jira] [Resolved] (LUCENE-7543) Make changes-to-html target an
offline operation
[ https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe resolved LUCENE-7543.
--------------------------------
Resolution: Fixed
Assignee: Steve Rowe
Fix Version/s: 6.3.1
6.4
6.2.2
5.5.4
5.6
6.1.1
6.0.2
master (7.0)
Committed.
Thanks [~manokovacs]!
> Make changes-to-html target an offline operation
> ------------------------------------------------
>
> Key: LUCENE-7543
> URL: https://issues.apache.org/jira/browse/LUCENE-7543
> 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.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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org