update readme

Author: e-kotov

README.md

@@ -227,12 +227,13 @@ in progress).
 ## Limitations
 
 Currently, `rJavaEnv` only supports major `Java` versions such as 8, 11,
-17, 21, 22. The download and install functions ignore the minor version
-of the `Java` distribution and just downloads the latest stable
-subversion of the specified major version. This is done to simplify the
-process and avoid the need to update the package every time a new minor
-version of `Java` is released. For most users this should be sufficient,
-but this is substandard for full reproducibility.
+15 to 24 and any newer version. The download and install functions
+ignore the minor version of the `Java` distribution and just downloads
+the latest stable subversion of the specified major version. This is
+done to simplify the process and avoid the need to update the package
+every time a new minor version of `Java` is released. For most users
+this should be sufficient, but this is substandard for full
+reproducibility.
 
 The main limitation is that if you want to switch to another `Java`
 environment, you will most likely have to restart the current R session

README.qmd

@@ -180,7 +180,7 @@ For detailed usage, see the [Quick Start Vignette](https://www.ekotov.pro/rJavaE
 
 ## Limitations
 
-Currently, `rJavaEnv` only supports major `Java` versions such as 8, 11, 17, 21, 22. The download and install functions ignore the minor version of the `Java` distribution and just downloads the latest stable subversion of the specified major version. This is done to simplify the process and avoid the need to update the package every time a new minor version of `Java` is released. For most users this should be sufficient, but this is substandard for full reproducibility.
+Currently, `rJavaEnv` only supports major `Java` versions such as 8, 11, 15 to 24 and any newer version. The download and install functions ignore the minor version of the `Java` distribution and just downloads the latest stable subversion of the specified major version. This is done to simplify the process and avoid the need to update the package every time a new minor version of `Java` is released. For most users this should be sufficient, but this is substandard for full reproducibility.
 
 The main limitation is that if you want to switch to another `Java` environment, you will most likely have to restart the current R session and set the `JAVA_HOME` and `PATH` environment variables to the desired `Java` environment using `rJavaEnv::java_env_set()`. This cannot be done dynamically within the same R session due to the way Java is initialized in R, particularly with the `rJava`-dependent packages such as [`r5r`](https://github.com/ipeaGIT/r5r){target="_blank"}. With packages like [`opentripplanner`](https://github.com/ropensci/opentripplanner){target="_blank"}, that performs `Java` calls using command line, you can switch `Java` environments dynamically within the same R session as much as you want.