[
https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838227#comment-15838227
]
Steve Rowe edited comment on LUCENE-7543 at 1/25/17 5:42 PM:
-------------------------------------------------------------
>From [~arafalov] on the dev list:
{quote}
I just noticed that in the HTML version of the shipped release notes,
the "LUCENE_CHANGES.txt" is no longer hyperlinked to the online
version of the Lucene changes document.
In the 6.3 release and before, it was hyperlinked.
{quote}
The issue: Changes committed on this issue changed the product name
“SOLR”->”solr” passed by {{solr/build.xml}} into {{changes2html.pl}}, which
causes the conditional code to do the LUCENE_CHANGES.txt hyperlinking to never
get invoked because the product name is misspelled… Not sure why the product
name got downcased?
was (Author: steve_rowe):
>From [~arafalov] on the dev list:
{quote}
I just noticed that in the HTML version of the shipped release notes,
the "LUCENE_CHANGES.txt" is no longer hyperlinked to the online
version of the Lucene changes document.
In the 6.3 release and before, it was hyperlinked.
{quote}
The issue: Changes committed on this issues the product name “SOLR”->”solr”
passed into {{changes2html.pl}}, which now causes the conditional code to do
the LUCENE_CHANGES.txt hyperlinking to never get invoked because the product
name is misspelled… Not sure why the product name got downcased?
> 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-drop-XML-Simple.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
