Update www.eclipse.org/openj9/ to eclipse.dev/openj9/

pshipton · pshipton · commit cc81dd80cb55 · 2025-11-06T17:03:03.000-05:00
Also update an obsolete link to join slack. The old address is currently
redirected, but the new address should be used.

Signed-off-by: Peter Shipton &lt;Peter_Shipton@ca.ibm.com&gt;
diff --git a/.github/ISSUE_TEMPLATE/documentation-error.md b/.github/ISSUE_TEMPLATE/documentation-error.md
@@ -6,6 +6,6 @@ about: For inaccuracies in existing topics, including typos.
 
 **Page containing the error:**
 
-*www.eclipse.org/openj9/docs/*
+*eclipse.dev/openj9/docs/*
 
 **Describe the error and the update needed:**
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -132,7 +132,7 @@ Some examples:
 
 For consistency across the user documentation, there are a few style guidelines that you should follow.
 These are not set in stone, so if you have any suggestions or concerns, open up a discussion in the [Slack channel](https://openj9.slack.com/).
-If you haven't done so already, [join the channel](https://www.eclipse.org/openj9/oj9_joinslack.html).
+If you haven't done so already, [join the channel](https://openj9.slack.com/join/shared_invite/enQtNDU4MDI4Mjk0MTk2LWVhNTMzMGY1N2JkODQ1OWE0NTNmZjM4ZDcxOTBiMjk3NGFjM2U0ZDNhMmY0MDZlNzU0ZjAyNzQ1ODlmYjg3MjA).
 
 Generally, follow the style and structure of existing topics.
 If you are creating a new topic, you might find it helpful to copy a similar existing topic and modify it. (Don't forget to modify the file name in the footer!)
@@ -353,6 +353,6 @@ You can publish the OpenJ9 documents when the release is created. You need not w
 
 When released, the latest version of Eclipse OpenJ9 is published at:
 
-https://www.eclipse.org/openj9/docs
+https://eclipse.dev/openj9/docs
 
 For more information about the documentation release process, build process, and publication process, see the wiki section of this repository.
diff --git a/JenkinsFile_build_doc.groovy b/JenkinsFile_build_doc.groovy
@@ -110,14 +110,14 @@ timeout(time: 6, unit: 'HOURS') {
                                 // If a pull request, use staging site banner
                                 sh """
                                     cp /myenv/lib/python3.10/site-packages/material/templates/base.html theme/base.html
-                                    sed -i 's|{% block hero %}|<!--Staging site notice --><div class="md-container"><div style="margin:-2rem 0 -2rem 0; background: linear-gradient(white, #69c1bd, white); color:white; text-align:center; font-size:1.5rem; font-weight:bold; text-shadow: 2px 2px 4px #000000;"><p style="padding:2rem 0 2rem 0;"><i class="fa fa-exclamation-triangle" aria-hidden="true"></i> CAUTION: This site is for reviewing draft documentation. For published content, visit <a style="color:#af6e3d; text-shadow:none; padding-left:1rem;" href="http://www.eclipse.org/openj9/docs/index.html">www.eclipse.org/openj9/docs</a></p></div>{% block hero %}|' theme/base.html
+                                    sed -i 's|{% block hero %}|<!--Staging site notice --><div class="md-container"><div style="margin:-2rem 0 -2rem 0; background: linear-gradient(white, #69c1bd, white); color:white; text-align:center; font-size:1.5rem; font-weight:bold; text-shadow: 2px 2px 4px #000000;"><p style="padding:2rem 0 2rem 0;"><i class="fa fa-exclamation-triangle" aria-hidden="true"></i> CAUTION: This site is for reviewing draft documentation. For published content, visit <a style="color:#af6e3d; text-shadow:none; padding-left:1rem;" href="http://eclipse.dev/openj9/docs/index.html">eclipse.dev/openj9/docs</a></p></div>{% block hero %}|' theme/base.html
                                     """
                             }
                             else if (params.BUILD_TYPE != "RELEASE") {
                                 // Otherwise, and if this isn't for a release, use ghpages site banner
                                 sh """
                                     cp /myenv/lib/python3.10/site-packages/material/templates/base.html theme/base.html
-                                    sed -i 's|{% block hero %}|<!--Ghpages site notice --><div class="md-container"><div style="margin:-2rem 0 -2rem 0; background: linear-gradient(white, #ffa02e, white); color:white; text-align:center; font-size:1.5rem; font-weight:bold; text-shadow: 2px 2px 4px #000000;"><p style="padding:2rem 0 2rem 0;"><i class="fa fa-cogs" aria-hidden="true"></i> CAUTION: This site hosts draft documentation for the next release. For published content of the latest release, visit <a style="color:#af6e3d; text-shadow:none; padding-left:1rem;" href="http://www.eclipse.org/openj9/docs/index.html">www.eclipse.org/openj9/docs</a></p></div>{% block hero %}|' theme/base.html
+                                    sed -i 's|{% block hero %}|<!--Ghpages site notice --><div class="md-container"><div style="margin:-2rem 0 -2rem 0; background: linear-gradient(white, #ffa02e, white); color:white; text-align:center; font-size:1.5rem; font-weight:bold; text-shadow: 2px 2px 4px #000000;"><p style="padding:2rem 0 2rem 0;"><i class="fa fa-cogs" aria-hidden="true"></i> CAUTION: This site hosts draft documentation for the next release. For published content of the latest release, visit <a style="color:#af6e3d; text-shadow:none; padding-left:1rem;" href="http://eclipse.dev/openj9/docs/index.html">eclipse.dev/openj9/docs</a></p></div>{% block hero %}|' theme/base.html
                                     """
                             }
 
diff --git a/README.md b/README.md
@@ -32,14 +32,14 @@
 [![License](https://img.shields.io/badge/License-EPL%202.0-green.svg)](https://opensource.org/licenses/EPL-2.0)
 [![License](https://img.shields.io/badge/License-APL%202.0-green.svg)](https://opensource.org/licenses/Apache-2.0)
 
-This repository contains the source files for the [Eclipse OpenJ9 user documentation](http://www.eclipse.org/openj9/docs).
+This repository contains the source files for the [Eclipse OpenJ9 user documentation](http://eclipse.dev/openj9/docs).
 The user documentation tells you how to configure, tune, and diagnose problems with
 an OpenJDK that has been built with the OpenJ9 Java virtual machine.
 
 New to Eclipse OpenJ9? Here are a few links to get you started:
 
-- Visit the [Eclipse OpenJ9 website](http://www.eclipse.org/openj9) to find out more.
-- Read the [Getting started](https://www.eclipse.org/openj9/docs/introduction/) topic in our user documentation.
+- Visit the [Eclipse OpenJ9 website](http://eclipse.dev/openj9) to find out more.
+- Read the [Getting started](https://eclipse.dev/openj9/docs/introduction/) topic in our user documentation.
 
 The files in this repository are authored in markdown format and built using
 [Mkdocs](http://www.mkdocs.org/) with the [MkDocs-material theme](https://squidfunk.github.io/mkdocs-material/). Draft documentation for the next release is hosted via the gh-pages branch of this repository at the following URL: https://eclipse-openj9.github.io/openj9-docs/).
diff --git a/docs/index.md b/docs/index.md
@@ -48,13 +48,13 @@ OpenJDK binaries that contain the OpenJ9 VM are supported on a range of hardware
 
 Several versions of the documentation are available, covering all releases of OpenJ9:
 
-- [Online documentation for the last release](https://www.eclipse.org/openj9/docs/index.html)
+- [Online documentation for the last release](https://eclipse.dev/openj9/docs/index.html)
 - [Online, in-progress documentation for the forthcoming release](https://eclipse-openj9.github.io/openj9-docs/)
 - [Downloads of earlier releases](https://github.com/eclipse-openj9/openj9-docs/tree/master/downloads): to download a zip file, click the filename, then click **Download**. After downloading a `.zip` file, extract it, then open the `index.html` file in your browser.
 
 ## Useful links
 
-- [Eclipse OpenJ9 website home page](https://www.eclipse.org/openj9)
+- [Eclipse OpenJ9 website home page](https://eclipse.dev/openj9)
 - [Eclipse OpenJ9 GitHub repository](https://github.com/eclipse-openj9/openj9)
 - [Eclipse Foundation OpenJ9 project page](https://projects.eclipse.org/projects/technology.openj9)
 
diff --git a/docs/jitserver_tuning.md b/docs/jitserver_tuning.md
@@ -35,7 +35,7 @@ The client-session caches are deleted when the clients terminate, but this can h
 ### JITServer AOT cache
 
  The JITServer technology can cache AOT compiled methods at the server.
- The JITServer can, therefore, avoid carrying out an AOT compilation when a compatible AOT method body already exists in the cache, thereby saving CPU resource and improving remote compilation latency. This mechanism uses the [dynamic AOT technology](https://www.eclipse.org/openj9/docs/aot/), but does not require a shared class cache at the client.<!-- and therefore the client needs to have the [shared classes cache](https://www.eclipse.org/openj9/docs/shrc/) (SCC) enabled (the SCC is the repository for the AOT code) Deleted this content because from the 0.46.0 release onwards the local SCC is ignored by default -->
+ The JITServer can, therefore, avoid carrying out an AOT compilation when a compatible AOT method body already exists in the cache, thereby saving CPU resource and improving remote compilation latency. This mechanism uses the [dynamic AOT technology](https://eclipse.dev/openj9/docs/aot/), but does not require a shared class cache at the client.<!-- and therefore the client needs to have the [shared classes cache](https://eclipse.dev/openj9/docs/shrc/) (SCC) enabled (the SCC is the repository for the AOT code) Deleted this content because from the 0.46.0 release onwards the local SCC is ignored by default -->
 
  When the JITServer receives an AOT compilation request, it checks its AOT cache for a compatible compiled method body. If one is not found, the server performs the AOT compilation, sends the response to the client JVM, then serializes the compiled method and stores it in its local AOT cache, for future use. If a compatible compiled method is found, the server sends the client the serialized compiled method from its cache, thus avoiding a compilation. The client deserializes the response and loads the compiled method as a regular dynamic AOT code.
 
diff --git a/docs/openj9_newuser.md b/docs/openj9_newuser.md
@@ -51,7 +51,7 @@ In other cases, tools have been added for compatibility with the reference imple
 OpenJ9 contains extensive trace and debugging capabilities to help identify, isolate, and solve run time problems.
 
 - **Dump files:** Various types of dump are produced by default in response to certain events and can also be triggered for a whole range of events by using the `com.ibm.jvm.Dump` API or by specifying `-Xdump` options on the command line. Dumps include [Java dumps](dump_javadump.md), [heap dumps](dump_heapdump.md), [system dumps](dump_systemdump.md), JIT dumps, stack dumps, and snap dumps (tracepoint data). For more information, see the [`-Xdump`](xdump.md) option.
-- **Verbose log files:** Some components of OpenJ9 can also produce verbose output or log files to assist with problem determination, including [class data sharing](https://www.eclipse.org/openj9/docs/xshareclasses/#printallstats-cache-utility), [garbage collection](https://www.eclipse.org/openj9/docs/gc/#troubleshooting), and the [JIT compiler](https://www.eclipse.org/openj9/docs/xjit/#verbose).
+- **Verbose log files:** Some components of OpenJ9 can also produce verbose output or log files to assist with problem determination, including [class data sharing](https://eclipse.dev/openj9/docs/xshareclasses/#printallstats-cache-utility), [garbage collection](https://eclipse.dev/openj9/docs/gc/#troubleshooting), and the [JIT compiler](https://eclipse.dev/openj9/docs/xjit/#verbose).
 - **Trace files:** The OpenJ9 implementation contains extensive tracepoints used to log information and exceptional conditions, with minimal impact on performance. Some tracepoints are enabled by default; others can be enabled on demand. For more information, see the [`-Xtrace`](xtrace.md) option for tracing Java applications and the VM, and the [`-Xtgc`](xtgc.md) option for tracing garbage collection.
 
 If you are familiar with using HotSpot as part of an Oracle JDK or OpenJDK, you probably make use of the monitoring and diagnostic tools that are provided with the VM. OpenJ9 has implemented a different approach to providing similar data; rather than running a number of different tools to obtain a different piece of information, the Java dump file provides a comprehensive set of information in one place. You can find the following information in an OpenJ9 Java dump:
diff --git a/docs/openj9_releases.md b/docs/openj9_releases.md
@@ -24,7 +24,7 @@
 # Overview
 
 
-New releases of Eclipse OpenJ9&trade; are set to coincide with critical patch updates and new versions of the Java&trade; SE class libraries. To learn more about when these releases take place, and the OpenJ9 support lifecycle, see [Supported environments](https://www.eclipse.org/openj9/docs/openj9_support/).
+New releases of Eclipse OpenJ9&trade; are set to coincide with critical patch updates and new versions of the Java&trade; SE class libraries. To learn more about when these releases take place, and the OpenJ9 support lifecycle, see [Supported environments](https://eclipse.dev/openj9/docs/openj9_support/).
 
 If you are interested in the content of future releases, plans are published in the [Eclipse OpenJ9 project page](https://projects.eclipse.org/projects/technology.openj9).
 
diff --git a/docs/version0.37.md b/docs/version0.37.md
@@ -57,7 +57,7 @@ Linux builds for platforms Linux x86 64-bit, Linux on POWER LE 64-bit, and Linux
 
 ### Support added for the `com.sun.management.ThreadMXBean` interface
 
-The OpenJ9 [`ThreadMXbean` interface](https://www.eclipse.org/openj9/docs/api-langmgmt/) (`com.ibm.lang.management.ThreadMXBean`) was extending the [`java.lang.management.ThreadMXBean`](https://docs.oracle.com/javase/8/docs/api/java/lang/management/ThreadMXBean.html) interface. With this release, the OpenJ9 `ThreadMXBean` interface extends the [`com.sun.management.ThreadMXBean`](https://docs.oracle.com/javase/8/docs/jre/api/management/extension/com/sun/management/ThreadMXBean.html) interface, whereby it now contains all the methods of the `java.lang.management.ThreadMXBean` interface with additional methods from the `com.sun.management.ThreadMXBean` interface.
+The OpenJ9 [`ThreadMXbean` interface](https://eclipse.dev/openj9/docs/api-langmgmt/) (`com.ibm.lang.management.ThreadMXBean`) was extending the [`java.lang.management.ThreadMXBean`](https://docs.oracle.com/javase/8/docs/api/java/lang/management/ThreadMXBean.html) interface. With this release, the OpenJ9 `ThreadMXBean` interface extends the [`com.sun.management.ThreadMXBean`](https://docs.oracle.com/javase/8/docs/jre/api/management/extension/com/sun/management/ThreadMXBean.html) interface, whereby it now contains all the methods of the `java.lang.management.ThreadMXBean` interface with additional methods from the `com.sun.management.ThreadMXBean` interface.
 
 The OpenJ9 VM implementation does not support thread memory allocation measurement (`isThreadAllocatedMemorySupported` method returns false).
 
diff --git a/docs/version0.46.md b/docs/version0.46.md
@@ -63,7 +63,7 @@ The `getTotalThreadAllocatedBytes()` method now returns the total thread allocat
 
 `-XX:+JITServerUseAOTCache` is the default setting at the JITServer server now. That means that you don't have to specify the `-XX:+JITServerUseAOTCache` option at the server to enable the JITServer AOT caching feature.
 
-Although this option is by default enabled at the server, it is still disabled for the JITServer clients. The clients that want to use the JITServer AOT caching, must still specify the `-XX:+JITServerUseAOTCache` option on the command line. Also, now the clients don't have to enable the [shared classes cache](https://www.eclipse.org/openj9/docs/shrc/) feature to use the `-XX:+JITServerUseAOTCache` option.
+Although this option is by default enabled at the server, it is still disabled for the JITServer clients. The clients that want to use the JITServer AOT caching, must still specify the `-XX:+JITServerUseAOTCache` option on the command line. Also, now the clients don't have to enable the [shared classes cache](https://eclipse.dev/openj9/docs/shrc/) feature to use the `-XX:+JITServerUseAOTCache` option.
 
 For more information, see [ `-XX:[+|-]JITServerUseAOTCache`](xxjitserveruseaotcache.md).
 
diff --git a/docs/xdump.md b/docs/xdump.md
@@ -30,7 +30,7 @@ A large set of options and suboptions are available for controlling dumps, which
 
 ## Xdump Option Builder
 
-Use the <a href="https://www.eclipse.org/openj9/tools/xdump_option_builder.html" target="_blank">Xdump Option Builder tool</a> to help you specify the correct options and avoid incompatibilities.
+Use the <a href="https://eclipse.dev/openj9/tools/xdump_option_builder.html" target="_blank">Xdump Option Builder tool</a> to help you specify the correct options and avoid incompatibilities.
 
 ## Syntax
 
diff --git a/docs/xshareclasses.md b/docs/xshareclasses.md
@@ -449,7 +449,7 @@ behavior, which can improve the performance of class loading from the shared cla
 
 :   :fontawesome-solid-pencil:{: .note aria-hidden="true"} **Notes:**
 
-:    - With the 31-bit VM on all versions of z/OS, the shared cache is memory mapped within the 0-2 GB address range. The maximum size of the persistent shared classes cache is limited by the system limit `MAXMMAPAREA`. For more information about the suggested value for the `MAXMMAPAREA` limit, see [Setting resource limits (z/OS)](https://www.eclipse.org/openj9/docs/configuring/#setting-resource-limits-zos).
+:    - With the 31-bit VM on all versions of z/OS, the shared cache is memory mapped within the 0-2 GB address range. The maximum size of the persistent shared classes cache is limited by the system limit `MAXMMAPAREA`. For more information about the suggested value for the `MAXMMAPAREA` limit, see [Setting resource limits (z/OS)](https://eclipse.dev/openj9/docs/configuring/#setting-resource-limits-zos).
      - With the 64-bit VM, the shared cache is mapped as follows:
          - On z/OS version 2.3 and earlier, the persistent shared cache is memory mapped within the 0-2 GB address range. The maximum size of the persistent shared classes cache is limited by the system limit `MAXMMAPAREA`.
          - On z/OS version 2.4 and later, the persistent shared cache is mapped above the 2 GB address range. The maximum size of persistent shared classes cache is limited by the `MAXSHARE` value within the `SMFLIMxx` member of `SYS1.PARMLIB`. The default persistent shared cache size is 300MB, and the following machine configuration settings will allow a shared cache up to that size.
diff --git a/docs/xtrace.md b/docs/xtrace.md
@@ -31,7 +31,7 @@ Trace data can be output in human-readable or in compressed binary formats. The
 
 ## Xtrace Option Builder
 
-Use the <a href="https://www.eclipse.org/openj9/tools/xtrace_option_builder.html" target="_blank">Xtrace Option Builder tool</a> to help you specify the correct options and avoid incompatibilities.
+Use the <a href="https://eclipse.dev/openj9/tools/xtrace_option_builder.html" target="_blank">Xtrace Option Builder tool</a> to help you specify the correct options and avoid incompatibilities.
 
 ## Syntax
 
diff --git a/docs/xxenablecriusupport.md b/docs/xxenablecriusupport.md
@@ -69,7 +69,7 @@
 
 ## Explanation
 
-When you enable the option, the VM starts with the support for checkpoint and restore processes. The VM starts the JIT, GC, Security, and other internal components that make the checkpoint and restore points feasible. The option enables the use of `org.eclipse.openj9.criu.CRIUSupport` APIs. With CRIU support, you can take a checkpoint of the VM and restore the checkpoint image. When you specify the `-XX:+EnableCRIUSupport` option, the VM generates only those compiled codes that are portable (see [`-XX:[+|-]PortableSharedCache`](https://www.eclipse.org/openj9/docs/xxportablesharedcache/)) to facilitate restoring of the checkpoint image in multiple environments. VM does not load any code from the shared classes cache that is nonportable pre-checkpoint.
+When you enable the option, the VM starts with the support for checkpoint and restore processes. The VM starts the JIT, GC, Security, and other internal components that make the checkpoint and restore points feasible. The option enables the use of `org.eclipse.openj9.criu.CRIUSupport` APIs. With CRIU support, you can take a checkpoint of the VM and restore the checkpoint image. When you specify the `-XX:+EnableCRIUSupport` option, the VM generates only those compiled codes that are portable (see [`-XX:[+|-]PortableSharedCache`](https://eclipse.dev/openj9/docs/xxportablesharedcache/)) to facilitate restoring of the checkpoint image in multiple environments. VM does not load any code from the shared classes cache that is nonportable pre-checkpoint.
 
 Taking a checkpoint and restoring the checkpoint image generally happens on different environments with different behaviors. OpenJ9 makes compensations for such differences to ensure successful restore. For example, the VM compensates for the downtime between checkpoint and restore for elapsed time sensitive APIs such as `System.nanotime()` and `java.util.Timer`.
 
diff --git a/docs/xxjitserveruseaotcache.md b/docs/xxjitserveruseaotcache.md
diff --git a/mkdocs.yml b/mkdocs.yml
diff --git a/theme/partials/footer.html b/theme/partials/footer.html
