You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows binary/source install omits JRI.jar after JRI moved to src/jri — configure.win still checks top-level jri/configure.win #355
Summary:
On Windows, recent rJava installs (e.g. 1.0-18 with R 4.6.1 ucrt) ship only JRIEngine.jar and REngine.jar under system.file("jri", package = "rJava"), but not JRI.jar or jri.dll. Packages that still depend on the legacy JRI API (e.g. gMCP’s graphGUI(), which references org.rosuda.JRI.RMainLoopCallbacks) fail with java.lang.NoClassDefFoundError: org/rosuda/JRI/RMainLoopCallbacks and gMCP’s warning that JRI.jar is missing from the classpath.
Expected:
A full JRI install under inst/jri/ including at least JRI.jar and the native jri.dll (as in older Windows builds, e.g. rJava 1.0-11), so JRI-based GUIs and code using org.rosuda.JRI.* continue to work.
Activity
r-suzuki commentedon Nov 17, 2026
I've submitted PR #356 to address this issue. I hope this helps.