[ 
https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664603#comment-15664603
 ] 

Steve Rowe commented on LUCENE-7543:
------------------------------------

Thaks hoss, +1 to all your suggestions - I'd forgotten about the ability to put 
the doap.rdf files wherever we wanted.

{quote}
bq. 2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ 
and solr/).
I would suggest they might make more sense in dev-tools? just a gut feeling.
{quote}

Sure, maybe {{dev-tools/doap/lucene/doap.rdf}} and 
{{dev-tools/doap/solr/doap.rdf}} - alternatively I guess we could rename them 
to {{lucene-doap.rdf}} and {{solr-doap.rdf}} and put them directly in 
{{dev-tools/}}, but I prefer the former.

> 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
>
> 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]

Reply via email to