Rhino is an implementation of JavaScript in Java.
Rhino is licensed under the MPL 2.0.
The current release is Rhino 1.7.15. Please see the Release Notes.
Rhino 1.7.15 | May 3, 2024 |
Rhino 1.7.14 | January 6, 2022 |
Rhino 1.7.13 | September 2, 2020 |
Rhino 1.7.12 | January 13, 2020 |
Rhino 1.7.11 | May 30, 2019 |
Rhino 1.7.10 | April 9, 2018 |
Rhino 1.7.9 | March 15, 2018 |
Rhino 1.7.8 | January 22, 2018 |
Rhino 1.7.7.2 | August 24, 2017 |
Rhino 1.7.7.1 | February 2, 2016 |
Rhino 1.7.7 | June 17, 2015 |
Rhino 1.7.6 | April 15, 2015 |
Rhino 1.7R5 | January 29, 2015 |
Compatibility table which shows which advanced JavaScript features from ES6, and ES2016+ are implemented in Rhino.
Information for script builders and embedders:
JavaDoc for all the APIs:
https://javadoc.io/doc/org.mozilla/rhino
Rhino 1.7.15 and before were primarily used in a single JAR called "rhino.jar".
Newer releases now organize the code using Java modules. There are four primary modules:
The release contains the following other modules, which are used while building and testing but which are not published to Maven Central:
Rhino requires Java 17 or higher to build. The "spotless" tool, which enforces code formatting, will not run on older Java versions and you will receive a warning. If in doubt, Java 21 works great.
Rhino runs on Java 11 and higher. The build tools use the "--release" flag to ensure that only features from Java 11 are used in the product.
The CI tools run the Rhino tests on Java 11, 17, and 21. Regardless of what version of Java you are building with, you can test on another Java version using the RHINO_TEST_JAVA_VERSION environment variable.
For normal development, you can build the code, run the static checks, and run all the tests like this:
git submodule init
git submodule update
./gradlew check
To just run the Rhino shell, you can do this from the top-level directory:
./gradlew run -q --console=plain
Alternately, you can build an all-in-one JAR and run that:
./gradlew :rhino-all:build
java -jar rhino-all/build/libs/rhino-all-1.7.16-SNAPSHOT.jar
You can also run the benchmarks:
./gradlew jmh
It is a good idea to test major changes on Java 11 before assuming that they will pass the CI tests. To do this, set the environment variable RHINO_TEST_JAVA_VERSION to the version that you want to test. For example:
RHINO_TEST_JAVA_VERSION=11 ./gradlew check
This will only work if Gradle can find a JDK of the appropriate version. You can troubleshoot this using the command:
./gradlew -q javaToolchains
Not all installers seem to put JDKs in the places where Gradle can find them. When in doubt, installatioons from Adoptium seem to work on most platforms.
The "Jacoco" coverage is enabled by default for the main published modules as well as the special "tests" module. Coverage is generated for each of the main projects separately and available by running
./gradlew jacocoTestReport
To see an aggregated coverage report for everything, which is probably what you want, run
./gradlew testCodeCoverageReport
The result is in: ./tests/build/reports/jacoco/testCodeCoverageReport/html
Ensure all tests are passing
Remove -SNAPSHOT
from version in gradle.properties
in project root folder
Create file gradle.properties
in $HOME/.gradle
folder with following properties. Populate them with maven repo credentials and repo location.
mavenUser=
mavenPassword=
mavenSnapshotRepo=
mavenReleaseRepo=
Run Gradle
task to publish artifacts to Maven Central.
./gradlew publish
Increase version and add -SNAPSHOT
to it in gradle.properties
in project root folder.
Push gradle.properties
to GitHub
If you are using a modular JDK that disallows the reflective access to
non-public fields (16 and later), you may need to configure the JVM with the
--add-opens
option to authorize the packages that your scripts shall use, for example:
--add-opens java.desktop/javax.swing.table=ALL-UNNAMED
This is not necessary just to build or test Rhino -- it may be necessary when embedding it depending on what your project does.
Most issues are managed on GitHub:
https://github.com/mozilla/rhino/issues
To submit a new PR, please use the following process:
If you are adding new capabilities to Rhino, you may be making more test262 tests pass, which is a good thing. Please see the instructions on how to update our test262 configuration.
Because of differences between Java and JavaScript, when testing on newer Java versions, many Unicode-related test262 tests appear to pass, but they will fail on Java 11. Please ignore these!
Code formatting was introduced in 2021. The "spotless" plugin will fail your build if you have changed any files that have not yet been reformatted. Please use "spotlessApply" to reformat the necessary files.
If you are the first person to touch a big file that spotless wants to make hundreds of lines of changes to, please try to put the reformatting changes alone into a single Git commit so that we can separate reformatting changes from more substantive changes.
Currently, you must be building on Java 17 or higher for Spotless to run.
GitHub is the best place to go with questions. For example, we use "GitHub discussions":