Workaround to get JRuby build working #582
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: James Couball jcouball@yahoo.com
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.
Description
This is a workaround for the problem in JRuby with the JDK being used as described in jruby/jruby#7182 where it is report that there is a bug in the JDK that causes JRuby to raise an error when opening the NULL device for write. The underlying JDK bug is reported and fixed in JDK-8285445 which is targeted to a July 2022 release.
In the meantime, the workaround adds the following environment variable
JAVA_OPTS: -Djdk.io.File.enableADS=true
to all build steps so JRuby can function. This setting is detailed in the JDK Patch 8u333 Release Notes