Update library loading search paths

#1405 Updated the Migrating from Java 11 to Java 17 topic with the change in the search for the library behavior. Formatting correction. Applicable for all platforms and added variables specific to the platforms. Changed system property name as java.library.path. Retained "-Djava.library.path" as the command line option. Closes #1405 Signed-off-by: Sreekala Gopakumar [email protected]
eclipse-openj9 · Sep 18, 2024 · 48f42a1 · 48f42a1
1 parent 6e1ec70
commit 48f42a1
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/docs/migrating11to17.md b/docs/migrating11to17.md
@@ -45,5 +45,7 @@ The following table lists the new OpenJ9 features and notable changes with the O
 
 | Features and changes  | OpenJ9 release|
 |-----------------------|---------------|
-|Linux builds for all platforms use gcc 10.3 instead of gcc 7.5. See the list of [build environments](openj9_support.md#build-environments).| 0.33.0  |
-|The default operating system stack size on x64 platforms is increased from 256 KB to 512 KB to accommodate vector support. You can change the operating system stack size by using the [-Xmso](xmso.md) option.| 0.33.0   |
+|The default operating system stack size on x64 platforms is increased from 256 KB to 512 KB to accommodate vector support. You can change the operating system stack size by using the [-Xmso](xmso.md) option.|  0.33.0   |
+|When the VM loads an application native library (DLL), it searches for the library in the path that is specified in the `java.library.path` system property or in the following environment variables:<ul><li>`LIBPATH` - z/OS&reg; and AIX&reg;</li><li>`LD_LIBRARY_PATH` - Linux&reg;<li>`PATH` - Windows&trade;</li></ul><br>In Java 11 and earlier versions, the VM searched for the application native libraries by using both the `java.library.path` system property and the environment variable.<br>From Java 17 onwards, the search is based on only the `java.library.path` system property value that is obtained when the VM starts. Changing the `java.library.path` system property value after VM startup doesn't change the search. If the path is set on the command line by using the `-Djava.library.path` option, only this path is used for the search. The path that is specified by the environment variable is not used to search for the application native libraries.<br>The default value of the `java.library.path` system property is still derived from the environment variable.  |  0.29.1   |
+
+<!--|Linux builds for all platforms use gcc 10.3 instead of gcc 7.5. See the list of [build environments](openj9_support.md#build-environments).| 0.33.0  | (SG - Commented this in 0.47.0 release It is an out-of-date statement because both 11 and 17 use gcc 11.2 now.)-->