Releases: e-kotov/rJavaEnv
rJavaEnv 0.3.0
New features
-
Javaversion (currently still only forAmazon Corretto) is now determined dynamically using the official GitHubjsonwith releases, so when newJavaversion becomes available, you will not be depenent onrJavaEnvto be updated. As a fallback, versions up to 24 are hardcoded. -
Added
forceargument tojava_download(). When set toTRUE, allows to overwrite the distribution file if it already exist in the cache. This save the trouble of deleting the cached file withjava_clear()before re-downloading. -
Added a new function
java_valid_versions()allows to retrieve a list of all availableJavaversions for the current automatically detected OS and CPU architecture, or user-specified platform and architecture.
Improvements
-
Better command line
Javadetection (thanks to Jonas Lieth) -
Test coverage is now 7.2%
rJavaEnv 0.2.2
-
Hot fix: improve robustness of setting Java environment in the current session with either
use_java()orjava_quick_install(). See bug fix below. -
Bug fix: Setting Java environment via
rJava::.jniInitialized()rendered impossible changing Java version forrJava-dependent packages, because it somehow pre-initialisedrJava
rJavaEnv 0.2.1
-
Breaking change:
java_check_version_cmd()andjava_check_version_rjava()now return detectedJavaversion instead ofTRUE/FALSE -
New function
use_java()to download, install and setJavafrom cache for the current sesssion, without touching the current project/working directory. This is intended for use withtargetsandcallr. -
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. -
Documentation and description clean-up
rJavaEnv 0.1.2
- Fixed broken links in README.md
rJavaEnv v0.0.1
Initial version. Passing R CMD check.