[
https://issues.apache.org/jira/browse/LUCENE-9020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007460#comment-17007460
]
Uwe Schindler commented on LUCENE-9020:
---------------------------------------
Hi, sorry for delay. On Dec 3rd we already got a notification, but it was lost
in my inbox (I was out of office in London).
They will for now keep the current SVN repositiry and we can setup AliasMatches
as described:
bq. Please use /www/docs.lucene.apache.org/content/(solr|core) for your
aliasmatch, as that's a separate checkout of your svn path that will survive
the web site being moved to git.
I just asked if this also works on the staging server, so we can test it. If
this is true, I will modify the .htaccess file in GIT to add AliasMatches. At
the end we can deploy our javadocs and refguide at the usual place in SVN.
Once we moved to git, we should possibly cleanup the SVN tree and remove all
stuff that's not needed anymore, so only the static files survice. But this can
be done as a followup.
I am very sorry that I missed the notifications!!!
> Find a way to publish Solr RefGuide without checking into git
> -------------------------------------------------------------
>
> Key: LUCENE-9020
> URL: https://issues.apache.org/jira/browse/LUCENE-9020
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Priority: Major
>
> Currently we check in all versions of RefGuide (hundreds of small html files)
> into svn to publish as part of the site. With new site we should find a
> smoother way to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
