This is an automated email from the ASF dual-hosted git repository.

uschindler pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new d97f9f2  SOLR-15593: Update scripts and documentation to refer to new 
Javadocs/Refguide folder
d97f9f2 is described below

commit d97f9f20b093705e3a2fcdd2207e91b2e3bb13ca
Author: Uwe Schindler <[email protected]>
AuthorDate: Sun Aug 22 13:31:35 2021 +0200

    SOLR-15593: Update scripts and documentation to refer to new 
Javadocs/Refguide folder
---
 dev-docs/ref-guide/publish.adoc      | 4 ++--
 dev-tools/scripts/releaseWizard.yaml | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/dev-docs/ref-guide/publish.adoc b/dev-docs/ref-guide/publish.adoc
index d2b1a45..e136c1c 100644
--- a/dev-docs/ref-guide/publish.adoc
+++ b/dev-docs/ref-guide/publish.adoc
@@ -61,7 +61,7 @@ The HTML files themselves will be in 
`solr/solr-ref-guide/build/html-site`.
 Push the Guide directly to production via Subversion `import` from where you 
built it.
 
 [source,bash]
-svn -m "Add Ref Guide for Solr 7.7" import 
<checkoutroot>/solr/solr-ref-guide/build/html-site 
https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/7_7
+svn -m "Add Ref Guide for Solr 7.7" import 
<checkoutroot>/solr/solr-ref-guide/build/html-site 
https://svn.apache.org/repos/infra/sites/solr/guide/7_7
 
 Confirm you can browse to Guide manually by going to the new URL.
 For example: https://solr.apache.org/guide/7_7
@@ -91,7 +91,7 @@ Including the `-PsolrGuideDraft=false` property ensures the 
DRAFT watermark and
 . Checkout the directory you need to update from the svn production repo:
 +
 [source,bash]
-$ svn co 
https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/<dir>
+$ svn co https://svn.apache.org/repos/infra/sites/solr/guide/<dir>
 +
 * This command checks out the Guide version directory into a local 
subdirectory with the same name as the version (such as "7_7"). You can provide 
a better name locally if you prefer by adding it to the end of the command 
shown above.
 * Don't shortcut this and download the whole production website.
diff --git a/dev-tools/scripts/releaseWizard.yaml 
b/dev-tools/scripts/releaseWizard.yaml
index 29db1bc..71966fd 100644
--- a/dev-tools/scripts/releaseWizard.yaml
+++ b/dev-tools/scripts/releaseWizard.yaml
@@ -1060,11 +1060,11 @@ groups:
         cmd: "{{ gradle_cmd }} documentation -Dversion.release={{ 
release_version }}"
         comment: Build documentation
       - !Command
-        cmd: svn -m "Add docs, changes and javadocs for Lucene {{ 
release_version }}"  import {{ git_checkout_folder }}/lucene/build/docs  
https://svn.apache.org/repos/infra/websites/production/lucene/content/core/{{ 
version }}
+        cmd: svn -m "Add docs, changes and javadocs for Lucene {{ 
release_version }}"  import {{ git_checkout_folder }}/lucene/build/docs  
https://svn.apache.org/repos/infra/sites/lucene/core/{{ version }}
         logfile: add-docs-lucene.log
         comment: Add docs for Lucene
       - !Command
-        cmd: svn -m "Add docs, changes and javadocs for Solr {{ 
release_version }}"  import {{ git_checkout_folder }}/solr/build/docs  
https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/{{ 
version }}
+        cmd: svn -m "Add docs, changes and javadocs for Solr {{ 
release_version }}"  import {{ git_checkout_folder }}/solr/build/docs  
https://svn.apache.org/repos/infra/sites/solr/docs/{{ version }}
         logfile: add-docs-solr.log
         comment: Add docs for Solr
   - !Todo

Reply via email to