MLE-25780 Ruby docs updates

.copyrightconfig

@@ -10,4 +10,4 @@ startyear: 2018
 #   - Use sparingly (third_party, generated, binary assets)
 #   - Dotfiles already skipped automatically
 # Enable by removing the leading '# ' from the next line and editing values.
-filesexcluded: .github/*, docs/*, README.md, Jenkinsfile, gradle/*, docker-compose.yml, *.gradle, gradle.properties, gradlew, gradlew.bat, **/test/resources/**, *.md, *.txt
+filesexcluded: .github/*, docs/*, *.md, Jenkinsfile, gradle/*, *.yml, *.gradle, gradle.properties, gradlew, gradlew.bat, **/test/resources/**, *.md, *.txt, *version, *.lock

.github/workflows/jekyll-gh-pages.yml

@@ -1,8 +1,10 @@
-# Sample workflow for building and deploying a Jekyll site to GitHub Pages
-name: Deploy Jekyll with GitHub Pages dependencies preinstalled
+# Started with: https://github.com/actions/starter-workflows/blob/main/pages/jekyll.yml .
+# Have to use a custom Jekyll workflow as the default GitHub Jekyll workflow does not whitelist the
+# "jekyll-tabs" plugin that lets us show code tabs in the documentation.
+
+name: Deploy Jekyll site to Pages
 
 on:
-  # Runs on pushes targeting the default branch
   push:
     branches: ["master"]
 
@@ -21,23 +23,33 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  # Build job
   build:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
+      - name: Setup Ruby and install Gemfile bundles
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.3.4' # Matches GH Pages; keep explicit to match .ruby-version and make CI intent clear
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+          working-directory: ./docs
+          cache-version: 0 # Increment this number if you need to re-download cached gems
       - name: Setup Pages
-        uses: actions/configure-pages@v3
+        id: pages
+        uses: actions/configure-pages@v5
       - name: Build with Jekyll
-        uses: actions/jekyll-build-pages@v1
-        with:
-          source: ./docs/
-          destination: ./_site
+        working-directory: ./docs
+        # Outputs to the './_site' directory by default
+        run: bundle exec jekyll build --verbose --baseurl "${{ steps.pages.outputs.base_path }}"
+        env:
+          JEKYLL_ENV: production
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v1
+        # Automatically uploads an artifact from the './_site' directory by default
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: "./docs/_site"
 
-  # Deployment job
   deploy:
     environment:
       name: github-pages
@@ -47,4 +59,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v1
+        uses: actions/deploy-pages@v4

CONTRIBUTING.md

@@ -40,7 +40,7 @@ You can build and test the docs locally by
 though you don't need to perform all of those steps since some files generated by doing so are already in the
 `./docs` directory. You just need to do the following:
 
-1. Install the latest Ruby (rbenv works well for this).
+1. Install the latest Ruby 3.x (rbenv works well for this).
 2. Install Jekyll.
 3. Go to the docs directory - `cd ./docs` .
 4. Run `bundle install` (this may not be necessary due to Gemfile.lock being in version control).

README.md

@@ -1,5 +1,5 @@
-![GitHub release](https://img.shields.io/github/release/marklogic-community/marklogic-unit-test.svg)
-![GitHub last commit](https://img.shields.io/github/last-commit/marklogic-community/marklogic-unit-test.svg)
+![GitHub release](https://img.shields.io/github/release/marklogic/marklogic-unit-test.svg)
+![GitHub last commit](https://img.shields.io/github/last-commit/marklogic/marklogic-unit-test.svg)
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
 # Easy testing of custom MarkLogic modules
@@ -19,5 +19,5 @@ marklogic-unit-test includes the following components:
    popular Java testing frameworks. As of the 2.0.0 release, these now require Java 17 or higher. 
 4. A REST endpoint for integrating with testing frameworks in any language.
 
-Please see [the user guide](https://marklogic-community.github.io/marklogic-unit-test/) to get started with adding
+Please see [the user guide](https://marklogic.github.io/marklogic-unit-test/) to get started with adding
 marklogic-unit-test to your project.

docs/Gemfile.lock

@@ -24,10 +24,12 @@ GEM
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.8.1)
-    faraday (2.7.10)
-      faraday-net_http (>= 2.0, < 3.1)
-      ruby2_keywords (>= 0.0.4)
-    faraday-net_http (3.0.2)
+    faraday (2.14.1)
+      faraday-net_http (>= 2.0, < 3.5)
+      json
+      logger
+    faraday-net_http (3.4.2)
+      net-http (~> 0.5)
     ffi (1.15.5)
     forwardable-extended (2.6.0)
     gemoji (3.0.1)
@@ -196,6 +198,7 @@ GEM
       gemoji (~> 3.0)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
+    json (2.18.1)
     kramdown (2.3.2)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -204,15 +207,18 @@ GEM
     listen (3.8.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.7.0)
     mercenary (0.3.6)
     minima (2.5.1)
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
     minitest (5.19.0)
-    nokogiri (1.18.9-arm64-darwin)
+    net-http (0.9.1)
+      uri (>= 0.11.1)
+    nokogiri (1.19.1-arm64-darwin)
       racc (~> 1.4)
-    nokogiri (1.18.9-x86_64-linux-gnu)
+    nokogiri (1.19.1-x86_64-linux-gnu)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
@@ -226,7 +232,6 @@ GEM
       ffi (~> 1.0)
     rexml (3.4.2)
     rouge (3.26.0)
-    ruby2_keywords (0.0.5)
     rubyzip (2.3.2)
     safe_yaml (1.0.5)
     sass (3.7.4)
@@ -249,11 +254,13 @@ GEM
       unf_ext
     unf_ext (0.0.8.2)
     unicode-display_width (1.8.0)
+    uri (1.1.1)
     webrick (1.8.2)
 
 PLATFORMS
   arm64-darwin-21
   arm64-darwin-23
+  arm64-darwin-25
   x86_64-linux
 
 DEPENDENCIES

docs/_config.yml

@@ -9,8 +9,8 @@ logo: "/assets/ProgressMarkLogic_PrimaryLogo_Stacked.svg"
 
 # Aux links for the upper right navigation
 aux_links:
-  "marklogic-community/marklogic-unit-test":
-    - "https://github.com/marklogic-community/marklogic-unit-test"
+  "marklogic/marklogic-unit-test":
+    - "https://github.com/marklogic/marklogic-unit-test"
 
 # Makes Aux links open in a new tab. Default is false
 aux_links_new_tab: false

docs/assertion-functions.md

@@ -5,7 +5,7 @@ nav_order: 7
 ---
 
 The list below captures the assertion functions available in the marklogic-unit-test `/test/test-helper.xqy` module.
-You can also [browse the source code](https://github.com/marklogic-community/marklogic-unit-test/blob/master/marklogic-unit-test-modules/src/main/ml-modules/root/test/test-helper.xqy)
+You can also [browse the source code](https://github.com/marklogic/marklogic-unit-test/blob/master/marklogic-unit-test-modules/src/main/ml-modules/root/test/test-helper.xqy)
 for this module to examine these functions.
 
 ```

docs/getting-started.md

@@ -9,7 +9,7 @@ running a simple test.
 
 ## Example project description 
 
-The [example project](https://github.com/marklogic-community/marklogic-unit-test/tree/master/examples/getting-started)
+The [example project](https://github.com/marklogic/marklogic-unit-test/tree/master/examples/getting-started)
 for this guide is a simple MarkLogic application with a
 [custom REST endpoint](https://docs.marklogic.com/guide/rest-dev/extensions) named "thesaurus". The endpoint
 returns thesaurus entries via the `/example/lib.sjs` module located at `src/main/ml-modules/root` in the project.
@@ -66,7 +66,7 @@ The above configuration enables the ml-gradle `mlUnitTest` task to access the `m
 allowing it to run your marklogic-unit-test tests.
 
 If you are not using ml-gradle, you will need to manually add the marklogic-unit-test modules to your project. Please
-see [the marklogic-unit-test releases](https://github.com/marklogic-community/marklogic-unit-test/releases) for 
+see [the marklogic-unit-test releases](https://github.com/marklogic/marklogic-unit-test/releases) for 
 zip files containing these modules. 
 
 ## Writing a test

docs/index.md

@@ -29,5 +29,5 @@ If you have any questions or run into issues while using marklogic-unit-test, tr
 
 1. Check for a similar question [on Stack Overflow](https://stackoverflow.com/questions/tagged/marklogic).
 2. If you don't find a similar question, [ask one yourself](https://stackoverflow.com/questions/ask?tags=marklogic).
-3. Or [submit an issue](https://github.com/marklogic-community/marklogic-unit-test/issues/new); expect a response 
+3. Or [submit an issue](https://github.com/marklogic/marklogic-unit-test/issues/new); expect a response 
    within a day or two. 

docs/running-tests.md

@@ -50,14 +50,14 @@ tests. Any failed test will display a message capturing the assertion failure.
 
 ## Using JUnit5
 
-The [marklogic-junit5 library](https://github.com/marklogic-community/marklogic-unit-test/tree/master/marklogic-junit5) 
+The [marklogic-junit5 library](https://github.com/marklogic/marklogic-unit-test/tree/master/marklogic-junit5) 
 within this project provides support for testing REST endpoints in MarkLogic. It also supports running your 
 marklogic-unit-test tests as part of a JUnit test suite. This allows for a single test run to execute and report on 
 all of your tests - both your JUnit5 tests that invoke REST endpoints in MarkLogic and each of your marklogic-unit-test
 test modules.
 
 For further information, see 
-[the marklogic-junit5 example project](https://github.com/marklogic-community/marklogic-unit-test/tree/master/marklogic-junit5/examples/simple-ml-gradle)
+[the marklogic-junit5 example project](https://github.com/marklogic/marklogic-unit-test/tree/master/marklogic-junit5/examples/simple-ml-gradle)
 that describes the configuration necessary.
 
 ## Using the marklogic-unit-test REST extension

docs/writing-tests.md

@@ -7,7 +7,7 @@ nav_order: 3
 This guide is a reference on the different kinds of test modules, setup modules, and teardown modules you can write 
 and run with marklogic-unit-test. The examples shown in this page can be found
 in the `src/test/ml-modules/root/test/suites/thesaurus` directory in the
-[test-examples project](https://github.com/marklogic-community/marklogic-unit-test/tree/master/examples/test-examples).
+[test-examples project](https://github.com/marklogic/marklogic-unit-test/tree/master/examples/test-examples).
 
 ## Location of test files
 

marklogic-junit5/README.md

@@ -8,7 +8,7 @@ This library makes that as simple as possible by providing the following support
 configuration you've already defined in your project
 1. Clear your test database before a test run so it always runs in a known state
 1. Easily read and make assertions on JSON and XML documents, including support for XPath-based assertions
-1. Easily integrate [marklogic-unit-test](https://github.com/marklogic-community/marklogic-unit-test) tests into a JUnit test suite
+1. Easily integrate [marklogic-unit-test](https://github.com/marklogic/marklogic-unit-test) tests into a JUnit test suite
 
 Below is a simple example of a JUnit test that writes a couple documents, runs a search on them, and then reads them 
 back and verifies the contents of each document:
@@ -45,7 +45,7 @@ As of DHF 5.5, support exists within DHF 5 for writing tests and should be used
 See [this example project](https://github.com/marklogic/marklogic-data-hub/tree/master/examples/reference-entity-model#testing-support) 
 for more information.
 
-If you're using DHF 4, see [the DHF 4 example project](https://github.com/marklogic-community/marklogic-unit-test/tree/1.0.0/marklogic-junit5/examples/simple-dhf4)
+If you're using DHF 4, see [the DHF 4 example project](https://github.com/marklogic/marklogic-unit-test/tree/1.0.0/marklogic-junit5/examples/simple-dhf4)
 from the 1.0.0 tag of this repository. 
 
 ## Running the tests within this project

marklogic-junit5/build.gradle

@@ -44,7 +44,7 @@ publishing {
         name = "${group}:${project.name}"
         description = "Supports testing MarkLogic applications"
         packaging = "jar"
-        url = "https://github.com/marklogic-community/${project.name}"
+        url = "https://github.com/marklogic/${project.name}"
         licenses {
           license {
             name = "The Apache License, Version 2.0"
@@ -61,9 +61,9 @@ publishing {
           }
         }
         scm {
-          url = "git@github.com:marklogic-community/${project.name}.git"
-          connection = "scm:git@github.com:marklogic-community/${project.name}.git"
-          developerConnection = "scm:git@github.com:marklogic-community/${project.name}.git"
+          url = "git@github.com:marklogic/${project.name}.git"
+          connection = "scm:git@github.com:marklogic/${project.name}.git"
+          developerConnection = "scm:git@github.com:marklogic/${project.name}.git"
         }
       }
     }

marklogic-junit5/examples/simple-ml-gradle/README.md

@@ -1,6 +1,6 @@
 This project shows a basic setup for writing JUnit tests with marklogic-junit5 against an application deployed 
-with [ml-gradle](https://github.com/marklogic-community/ml-gradle). In addition, it includes an example of executing
-tests written using [marklogic-unit-test](https://github.com/marklogic-community/marklogic-unit-test) via JUnit.
+with [ml-gradle](https://github.com/marklogic/ml-gradle). In addition, it includes an example of executing
+tests written using [marklogic-unit-test](https://github.com/marklogic/marklogic-unit-test) via JUnit.
 
 ## Trying the project out locally
 

marklogic-junit5/src/main/java/com/marklogic/junit5/dhf/DataHubUnitTestsTest.java

@@ -1,5 +1,5 @@
 /*
- * Copyright (c) 2018-2025 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
+ * Copyright (c) 2018-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
  */
 package com.marklogic.junit5.dhf;
 
@@ -10,7 +10,7 @@
 
 /**
  * This is a JUnit 5 parameterized test that invokes every test module defined by the REST endpoint provided by the
- * marklogic-unit-test framework - https://github.com/marklogic-community/marklogic-unit-test . This class is abstract
+ * marklogic-unit-test framework - https://github.com/marklogic/marklogic-unit-test . This class is abstract
  * so that it is not run when executing tests for the marklogic-junit5 project - it is instead expected to be extended
  * in a project that depends on marklogic-junit5.
  * <p>

marklogic-junit5/src/main/java/com/marklogic/junit5/spring/MarkLogicUnitTestsTest.java

@@ -1,5 +1,5 @@
 /*
- * Copyright (c) 2018-2025 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
+ * Copyright (c) 2018-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
  */
 package com.marklogic.junit5.spring;
 
@@ -10,7 +10,7 @@
 
 /**
  * This is a JUnit 5 parameterized test that invokes every test module defined by the REST endpoint provided by the
- * marklogic-unit-test framework - https://github.com/marklogic-community/marklogic-unit-test . This class is abstract
+ * marklogic-unit-test framework - https://github.com/marklogic/marklogic-unit-test . This class is abstract
  * so that it is not run when executing tests for the marklogic-junit5 project - it is instead expected to be extended
  * in a project that depends on marklogic-junit5.
  * <p>

marklogic-unit-test-client/build.gradle

@@ -25,7 +25,7 @@ publishing {
         name = "${group}:${project.name}"
         description = "Supports testing MarkLogic applications"
         packaging = "jar"
-        url = "https://github.com/marklogic-community/${project.name}"
+        url = "https://github.com/marklogic/${project.name}"
         licenses {
           license {
             name = "The Apache License, Version 2.0"
@@ -42,9 +42,9 @@ publishing {
           }
         }
         scm {
-          url = "git@github.com:marklogic-community/${project.name}.git"
-          connection = "scm:git@github.com:marklogic-community/${project.name}.git"
-          developerConnection = "scm:git@github.com:marklogic-community/${project.name}.git"
+          url = "git@github.com:marklogic/${project.name}.git"
+          connection = "scm:git@github.com:marklogic/${project.name}.git"
+          developerConnection = "scm:git@github.com:marklogic/${project.name}.git"
         }
       }
     }

marklogic-unit-test-modules/build.gradle

@@ -35,7 +35,7 @@ publishing {
         name = "${group}:${project.name}"
         description = "Supports testing MarkLogic applications"
         packaging = "jar"
-        url = "https://github.com/marklogic-community/${project.name}"
+        url = "https://github.com/marklogic/${project.name}"
         licenses {
           license {
             name = "The Apache License, Version 2.0"
@@ -52,9 +52,9 @@ publishing {
           }
         }
         scm {
-          url = "git@github.com:marklogic-community/${project.name}.git"
-          connection = "scm:git@github.com:marklogic-community/${project.name}.git"
-          developerConnection = "scm:git@github.com:marklogic-community/${project.name}.git"
+          url = "git@github.com:marklogic/${project.name}.git"
+          connection = "scm:git@github.com:marklogic/${project.name}.git"
+          developerConnection = "scm:git@github.com:marklogic/${project.name}.git"
         }
       }
       artifact sourcesJar