Skip to content

Commit 2ae2bbe

Browse files
committed
fixup readme
1 parent a2b276c commit 2ae2bbe

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,18 +34,18 @@ of `Java`/`{rJava}`-dependent `R` packages such as `{r5r}`,
3434
`{tabulapdf}`, and many more. `{rJavaEnv}` prevents common problems like
3535
`Java` not found, `Java` version conflicts, missing `Java`
3636
installations, and the inability to install `Java` due to lack of
37-
administrative privileges. `rJavaEnv` automates the download,
37+
administrative privileges. `{rJavaEnv}` automates the download,
3838
installation, and setup of the `Java Development Kit` (`JDK`) on a
3939
per-project basis by setting the relevant `JAVA_HOME` in the current `R`
4040
session or the current working directory (via `.Rprofile`, with the
41-
user’s consent). Similar to what `renv` does for `R` packages,
42-
`rJavaEnv` allows different `Java` versions to be used across different
43-
projects, but can also be configured to allow multiple versions within
44-
the same project (e.g. with the help of `{targets}` package). **Note:
45-
there are a few extra steps for ‘Linux’ users, who don’t have any ‘Java’
46-
previously installed in their system, and who prefer package
47-
installation from source, rather then installing binaries from ‘Posit
48-
Package Manager’. See
41+
user’s consent). Similar to what `{renv}` does for `R` packages,
42+
`{rJavaEnv}` allows different `Java` versions to be used across
43+
different projects, but can also be configured to allow multiple
44+
versions within the same project (e.g. with the help of `{targets}`
45+
package). **Note: there are a few extra steps for ‘Linux’ users, who
46+
don’t have any ‘Java’ previously installed in their system, and who
47+
prefer package installation from source, rather then installing binaries
48+
from ‘Posit Package Manager’. See
4949
[documentation](https://www.ekotov.pro/rJavaEnv/articles/rJavaEnv.html#note-linux)
5050
for details.**
5151

README.qmd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ is_html <- knitr::is_html_output()
3434

3535
<!-- badges: end -->
3636

37-
Solve common issues with `Java` environment management in `R` for users of `Java`/`{rJava}`-dependent `R` packages such as `{r5r}`, `{opentripplanner}`, `{xlsx}`, `{openNLP}`, `{rWeka}`, `{RJDBC}`, `{tabulapdf}`, and many more. `{rJavaEnv}` prevents common problems like `Java` not found, `Java` version conflicts, missing `Java` installations, and the inability to install `Java` due to lack of administrative privileges. `rJavaEnv` automates the download, installation, and setup of the `Java Development Kit` (`JDK`) on a per-project basis by setting the relevant `JAVA_HOME` in the current `R` session or the current working directory (via `.Rprofile`, with the user's consent). Similar to what `renv` does for `R` packages, `rJavaEnv` allows different `Java` versions to be used across different projects, but can also be configured to allow multiple versions within the same project (e.g. with the help of `{targets}` package). **Note: there are a few extra steps for 'Linux' users, who don't have any 'Java' previously installed in their system, and who prefer package installation from source, rather then installing binaries from 'Posit Package Manager'. See [documentation](https://www.ekotov.pro/rJavaEnv/articles/rJavaEnv.html#note-linux) for details.**
37+
Solve common issues with `Java` environment management in `R` for users of `Java`/`{rJava}`-dependent `R` packages such as `{r5r}`, `{opentripplanner}`, `{xlsx}`, `{openNLP}`, `{rWeka}`, `{RJDBC}`, `{tabulapdf}`, and many more. `{rJavaEnv}` prevents common problems like `Java` not found, `Java` version conflicts, missing `Java` installations, and the inability to install `Java` due to lack of administrative privileges. `{rJavaEnv}` automates the download, installation, and setup of the `Java Development Kit` (`JDK`) on a per-project basis by setting the relevant `JAVA_HOME` in the current `R` session or the current working directory (via `.Rprofile`, with the user's consent). Similar to what `{renv}` does for `R` packages, `{rJavaEnv}` allows different `Java` versions to be used across different projects, but can also be configured to allow multiple versions within the same project (e.g. with the help of `{targets}` package). **Note: there are a few extra steps for 'Linux' users, who don't have any 'Java' previously installed in their system, and who prefer package installation from source, rather then installing binaries from 'Posit Package Manager'. See [documentation](https://www.ekotov.pro/rJavaEnv/articles/rJavaEnv.html#note-linux) for details.**
3838

3939

4040

0 commit comments

Comments
 (0)