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

paksyd pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/master by this push:
     new 2379189cc76 HBASE-29952 Clean up MathJax URI workaround from 
dev-support/jenkins-scripts/generate-hbase-website.sh (#7838)
2379189cc76 is described below

commit 2379189cc766450ae63d6e649d722ebfcac16bb8
Author: Dávid Paksy <[email protected]>
AuthorDate: Wed Mar 4 14:27:09 2026 +0100

    HBASE-29952 Clean up MathJax URI workaround from 
dev-support/jenkins-scripts/generate-hbase-website.sh (#7838)
    
    Now that the docs (RefGuide) is changed from AsciiDoc to new tech under 
HBASE-29878, we can get rid of the ugly workaround which replaced the MathJax 
CDN URI with local one in book.html before staging the website.
    
    Signed-off-by: Peter Somogyi <[email protected]>
    Signed-off-by: Nihal Jain <[email protected]>
    Reviewed by: Yurii Palamarchuk <[email protected]>
---
 dev-support/jenkins-scripts/generate-hbase-website.sh | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/dev-support/jenkins-scripts/generate-hbase-website.sh 
b/dev-support/jenkins-scripts/generate-hbase-website.sh
index 7a5661889a5..2ab7944fc66 100644
--- a/dev-support/jenkins-scripts/generate-hbase-website.sh
+++ b/dev-support/jenkins-scripts/generate-hbase-website.sh
@@ -191,14 +191,6 @@ else
   exit $status
 fi
 
-# Workaround to replace MathJax CDN URI with local one in book.html
-# There is no way to influence from where the book.html Asciidoc includes the 
MathJax.js library.
-# https://docs.asciidoctor.org/asciidoctor/latest/stem/mathjax/
-# 
https://docs.asciidoctor.org/asciidoc/latest/attributes/document-attributes-ref/
-# https://github.com/asciidoctor/asciidoctor/issues/761
-echo "Replace MathJax URI"
-sed -i 's,https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.9/,js/,g' 
"${component_dir}"/target/site/book.html
-
 # Stage the site
 echo "Staging HBase site"
 mvn \

Reply via email to