rJavaEnv 0.3.0
CRAN release: 2025-04-04
New features
Java
version (currently still only forAmazon Corretto
) is now determined dynamically using the official GitHubjson
with releases, so when newJava
version becomes available, you will not be depenent onrJavaEnv
to be updated. As a fallback, versions up to 24 are hardcoded.Added
force
argument 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 availableJava
versions for the current automatically detected OS and CPU architecture, or user-specified platform and architecture.
rJavaEnv 0.2.2 (2024-09-13)
CRAN release: 2024-09-13
Hot fix: improve robustness of setting
Java
environment in the current session with eitheruse_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.0 (2024-08-28)
Breaking change:
java_check_version_cmd()
andjava_check_version_rjava()
now return detectedJava
version instead ofTRUE
/FALSE
New function
use_java()
to download, install and setJava
from cache for the current sesssion, without touching the current project/working directory. This is intended for use withtargets
andcallr
.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.