submitted to cran

CRAN-SUBMISSION

@@ -0,0 +1,3 @@
+Version: 0.2.2
+Date: 2024-09-13 19:17:50 UTC
+SHA: bae1c6dea15b2f7750ae78d87ab0012a7772081f

cran-comments.md

@@ -1,22 +1,5 @@
-# Re-submission
+# rJavaEnv 0.2.2 (2024-09-13)
 
-## Update to 0.2.1
+* Hot fix: improve robustness of setting Java environment in the current session with either `use_java()` or `java_quick_install()`. See bug fix below.
 
-Brings new functions based on very quick user feedback after the first release.
-Also, hopefully, the new safeguarding with 'eval=false' in vignette will prevent erros on macos-oldrel https://cran.r-project.org/web/checks/check_results_rJavaEnv.html when vignette code is executed, even though the whole vignette is set no to evaluate the code.
-
-# rJavaEnv 0.2.1 (2024-09-03)
-
-* Documentation and description clean-up
-
-# rJavaEnv 0.2.0 (2024-08-28)
-
-* Improvement: `java_check_version_cmd()` and `java_check_version_rjava()` now return detected `Java` version instead of `TRUE`/`FALSE`. Note that this is a breaking change, but not critical given that the package has not obtained a significant user base yet.
-
-* New function `use_java()` to download, install and set `Java` from cache for the current sesssion, without touching the current project/working directory. This is intended for use with `targets` and `callr`.
-
-* New vignette on using the package with `targets' and 'callr`
-
-* Updated documentation with clearer instructions on cache folder cleanup before removing the package
-
-* Depends on `R` > 4.0 to be able to write to the package cache directory without extra user warning. Cache cleanup and management functions are provided, as well as the documentation in both README and vignettes.
+* Bug fix: Setting Java environment via `rJava::.jniInitialized()` rendered impossible changing Java version for `rJava`-dependent packages, because it somehow pre-initialised `rJava`