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

Hoss Man commented on LUCENE-7543:
----------------------------------

or just {{dev-tools/doap/lucene.rdf}} and {{dev-tools/doap/solr.rdf}} (with a 
{{README.txt}} in the same dir explaining to future devs why that dir is there) 
... or whatever names we like ... there's no rule that the filenames / URLs has 
to have "doap" in them ... the bike sheds can be any color we want.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to