rJava

Low-Level R to Java Interface

v1.0-16 · Mar 15, 2026 · LGPL-2.1

Description

Low-level interface to Java VM very much like .C/.Call and friends. Allows creation of objects, calling methods and accessing fields.

Downloads

103.6K

Last 30 days

341st

284.7K

Last 90 days

1.1M

Last year

Trend: +12.1% (30d vs prior 30d)

CRAN Check Status

3 ERROR

11 NOTE

Show all 14 flavors

Flavor	Status	Time
r-devel-linux-x86_64-debian-clang	NOTE	83.9s
r-devel-linux-x86_64-debian-gcc	NOTE	64.3s
r-devel-linux-x86_64-fedora-clang	NOTE	106s
r-devel-linux-x86_64-fedora-gcc	NOTE	105.7s
r-devel-macos-arm64	NOTE	27s
r-devel-windows-x86_64	NOTE	106s
r-oldrel-macos-arm64	ERROR	154s
r-oldrel-macos-x86_64	ERROR	76s
r-oldrel-windows-x86_64	NOTE	117s
r-patched-linux-x86_64	NOTE	78.1s
r-release-linux-x86_64	NOTE	73.7s
r-release-macos-arm64	ERROR	24s
r-release-macos-x86_64	NOTE	149s
r-release-windows-x86_64	NOTE	107s

Check details (39 non-OK)

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-clang

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-linux-x86_64-debian-clang

compiled code

Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-clang/Work/build/Packages/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackDir’, ‘R_CStackLimit’,
    ‘R_CStackStart’, ‘R_UnboundValue’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-devel-linux-x86_64-debian-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-gcc

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-linux-x86_64-debian-gcc

compiled code

Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackDir’, ‘R_CStackLimit’,
    ‘R_CStackStart’, ‘R_UnboundValue’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-devel-linux-x86_64-debian-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-clang

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-linux-x86_64-fedora-clang

compiled code

Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-clang/rJava.Rcheck/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackDir’, ‘R_CStackLimit’,
    ‘R_CStackStart’, ‘R_UnboundValue’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-devel-linux-x86_64-fedora-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-gcc

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-linux-x86_64-fedora-gcc

compiled code

Note: information on .o files is not available
File ‘/data/gannet/ripley/R/packages/tests-devel/rJava.Rcheck/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackDir’, ‘R_CStackLimit’,
    ‘R_CStackStart’, ‘R_UnboundValue’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-devel-linux-x86_64-fedora-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-macos-arm64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-macos-arm64

compiled code

Note: information on .o files is not available
File ‘/Volumes/Builds/packages/sonoma-arm64/results/4.6/rJava.Rcheck/rJava/libs/rJava.so’:
  Found ‘___stderrp’, possibly from ‘stderr’ (C)
  Found ‘___stdoutp’, possibly from ‘stdout’ (C)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

NOTE r-devel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-windows-x86_64

compiled code

Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.6/rJava/libs/x64/rJava.dll':
  Found '_exit', possibly from '_exit' (C)
  Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
File 'rJava/libs/x64/rJava.dll':
  Found non-API call to R: 'R_UnboundValue'

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.

NOTE r-devel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

ERROR r-oldrel-macos-arm64

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.4/rJava.Rcheck/00install.out’ for details.

ERROR r-oldrel-macos-x86_64

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.4/rJava.Rcheck/00install.out’ for details.

NOTE r-oldrel-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-oldrel-windows-x86_64

compiled code

Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.4/rJava/libs/x64/rJava.dll':
  Found '_exit', possibly from '_exit' (C)
  Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.

See 'Writing portable packages' in the 'Writing R Extensions' manual.

NOTE r-oldrel-windows-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-patched-linux-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-patched-linux-x86_64

compiled code

Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-patched-gcc/Work/build/Packages/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackDir’, ‘R_CStackLimit’,
    ‘R_CStackStart’, ‘R_UnboundValue’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-patched-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-linux-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-release-linux-x86_64

compiled code

Note: information on .o files is not available
File ‘/home/hornik/tmp/R.check/r-release-gcc/Work/build/Packages/rJava/libs/rJava.so’:
  Found ‘_exit’, possibly from ‘_exit’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)
File ‘rJava/libs/rJava.so’:
  Found non-API calls to R: ‘R_CStackLimit’, ‘R_CStackStart’

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.
Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.

NOTE r-release-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

ERROR r-release-macos-arm64

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/rJava.Rcheck/00install.out’ for details.

NOTE r-release-macos-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-release-macos-x86_64

compiled code

Note: information on .o files is not available
File ‘/Volumes/Builds/packages/big-sur-x86_64/results/4.5/rJava.Rcheck/rJava/libs/rJava.so’:
  Found ‘___stderrp’, possibly from ‘stderr’ (C)
  Found ‘___stdoutp’, possibly from ‘stdout’ (C)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

NOTE r-release-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-release-windows-x86_64

compiled code

Note: information on .o files for x64 is not available
File 'd:/Rcompile/CRANpkg/lib/4.5/rJava/libs/x64/rJava.dll':
  Found '_exit', possibly from '_exit' (C)
  Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs nor [v]sprintf. The detected symbols are linked into
the code but might come from libraries and not actually be called.

See 'Writing portable packages' in the 'Writing R Extensions' manual.

NOTE r-release-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jri/src/Makefile.win
  src/jri/src/win32/Makefile
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

Additional Issues

M1mac Details →

rchk Details →

Check History

ERROR 0 OK · 12 NOTE · 0 WARNING · 2 ERROR · 0 FAILURE Mar 10, 2026

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@r-project.org>’

Package installs .java files.
Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-fedora-clang

top-level files

Non-standard file/directory found at top level:
  ‘jri’

NOTE r-devel-linux-x86_64-fedora-gcc

top-level files

Non-standard file/directory found at top level:
  ‘jri’

NOTE r-devel-macos-arm64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-devel-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-patched-linux-x86_64

top-level files

Non-standard file/directory found at top level:
  ‘jri’

NOTE r-release-linux-x86_64

top-level files

Non-standard file/directory found at top level:
  ‘jri’

ERROR r-release-macos-arm64

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.5/rJava.Rcheck/00install.out’ for details.

NOTE r-release-macos-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-release-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

ERROR r-oldrel-macos-arm64

whether package can be installed

Installation failed.
See ‘/Volumes/Builds/packages/big-sur-arm64/results/4.4/rJava.Rcheck/00install.out’ for details.

NOTE r-oldrel-macos-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File ‘rJava/R/import.R’:
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File ‘rJava/R/jinit.R’:
  unlockBinding(x, .env)
  unlockBinding(x, pe)

NOTE r-oldrel-windows-x86_64

R code for possible problems

Found the following possibly unsafe calls:
File 'rJava/R/import.R':
  unlockBinding(IMPORTER, env = env)
  assignInNamespace(IMPORTER, importer, envir = env)
File 'rJava/R/jinit.R':
  unlockBinding(x, .env)
  unlockBinding(x, pe)

Reverse Dependencies (129)

depends

AntAngioCOOL CommonDataModel GreedyExperimentalDesign GreedyExperimentalDesignJARs ISM InSilicoVA JGR REPPlab RH2 RJDBC RJSDMX RMOA RNetLogo RSCAT arulesNBMiner bartMachineJARs corehunter glmulti helloJavaWorld iplots mwa qCBA rCBA rChoiceDialogs rGroovy rcdklibs restoptr rflsgen rgph rkafkajars rmcfs rsubgroup rviewgraph scagnostics sjdbc spcosa streamMOA venneuler xlsxjars

imports

AWR AWR.Kinesis BASiNET BEACH BeastJar CBSr ChoR CirceR Crossover DataQualityDashboard DatabaseConnector DatabaseConnectorJars DecorateR Deducer EvidenceSynthesis FeatureExtraction JavaGD NicheBarcoding OpenStreetMap RJDemetra RKEA RKEAjars RMOAjars RSP RWeka RWekajars Rcurvep RxnSim SqlRender XLConnect bartMachine bartMan beastier boilerpipeR coreNLP dialr dialrjars dsa enmSdmX fsdaR gMCP hive joinXL llama mailR mallet matchingMarkets mutossGUI openNLP openNLPdata r5r rapidraker rcdk rjd3bench rjd3jars rjd3providers rjd3toolkit rjd3tramoseats rjd3workspace rjd3x13 rjdqa rjdworkspace rrepast simplace staplr tabulapdf wordnet xlsx

Dependency Network

Version History

updated 1.0-16 ← 1.0-15 diff Mar 15, 2026

updated 1.0-15 ← 1.0-14 diff Mar 11, 2026

new 1.0-14 Mar 10, 2026

updated 1.0-14 ← 1.0-11 diff Jan 19, 2026

updated 1.0-11 ← 1.0-10 diff Jan 25, 2024

updated 1.0-10 ← 1.0-6 diff Dec 1, 2023

updated 1.0-6 ← 1.0-5 diff Dec 9, 2021

updated 1.0-5 ← 1.0-4 diff Sep 23, 2021

updated 1.0-4 ← 0.9-13 diff Apr 28, 2021

updated 0.9-13 ← 0.9-12 diff Jul 5, 2020

updated 0.9-12 ← 0.9-11 diff Mar 23, 2020

updated 0.9-11 ← 0.9-10 diff Mar 28, 2019

updated 0.9-10 ← 0.9-9 diff May 28, 2018

updated 0.9-9 ← 0.9-8 diff Oct 11, 2017

updated 0.9-8 ← 0.9-7 diff Jan 6, 2016

updated 0.9-7 ← 0.9-6 diff Jul 28, 2015

updated 0.9-6 ← 0.9-5 diff Dec 23, 2013

updated 0.9-5 ← 0.9-4 diff Dec 2, 2013

updated 0.9-4 ← 0.9-3 diff Mar 11, 2013

updated 0.9-3 ← 0.9-2 diff Dec 10, 2011

rJava

Description

Downloads

CRAN Check Status

Additional Issues

Check History

Reverse Dependencies (129)

depends

imports

suggests

Dependency Network

Version History