-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Refine opens with logo only when running on Java 16 #4106
Comments
Thanks a lot for any help guys, really stumped. |
Do you still have an environment variable in Windows set for |
Thanks for reporting this bug. Right, I suspect that your Java 16 is still somewhere on your PATH. |
Also, I've opened a separate issue #4108 for OpenRefine 3.5.1 where I'm seeing that if started with |
@P3rCo I don't know yet what is going on with our 3.5.1 release and Java 16. |
@thadguidry |
@ylan1 Expected (for now) |
@thadguidry |
@thadguidry @wetneb Confirming it doesn't work on Java 16.
Error in browser console:
OpenRefine version: 3.5.1beta. Console messages:
|
hi @thadguidry what's the ETA on this issue? Should I downgrade Java? |
@VladimirAlexiev Don't use >= Java 16 for now. No idea on ETA...maybe next Spring? probably. |
I agree this should be pretty high priority. Hopefully 3.5 should fix this. |
... and doesn't work with Java 16 or later versions (see issue [OpenRefine#4106](OpenRefine#4106))
... and doesn't work with Java 16 or later versions (see issue OpenRefine#4106). This PR is a duplicate of OpenRefine#4134: I wasn't sure whether I should edit `docs` or `versioned_docs`, so edited both.
Same problem. Had installed Minecraft Java which wanted a newer version of JDK which I installed 16.1. I previously only had Java Runtime 1.8. After I uninstalled JDK 16.1 I got it to work (both versions with java embedded and without since I had JRE 1.8 installed already) |
I've had a look at this and it's a significant chunk of work, which could involve upgrading quite a few libraries. In the process we can introduce all sorts of bugs / incompatibilities which will require extensive testing. So I don't think we should do this for 3.5, otherwise this will delay this release even more. |
Agree, so where do we do the work? In 4.0 branch? Or a 3.6 branch with expectations of 3.6 also including SDC work and other new features? I personally think that 4.0 might be better for all if we focus dev efforts all together into that branch and will make the merge nightmare much more reduced. My thoughts are that 4.0 can be our next target and with the mindset we release maybe 1 year from now with Java 16 compatible, SDC ext builtin, and working PLL and tuning. |
I need to do more research to find out what the problem actually is, so yes, 3.6 or 4.0 depending on the scale of the problem. |
Added a recommendation about JDK version to use. Build-test-run.md sugguested to install the latest JDK which let's you build OpenRefine, but running it does not work see: OpenRefine#4106 This might be frustrating for beginners not aware of this issue.
The blocker for this is Java 16 compatibility of the Rhino Javascript engine. We are waiting for 1.7.14 to be released (mozilla/rhino#966). |
Note that Spark is not compatible with Java 16 either. This should not be a blocker to release the 4.0 branch since we will not be running on Spark by default (but users who want to rely on this functionality will need Java 8 or 11). |
I see that this project is using the If that is the case (just guessing), and until the packaging of the Rhino project is modified (as part of a full modularisation that I have suggested, see mozilla/rhino#1075 (comment)), you could switch to the main |
Thanks for chiming in @carlosame. I am a bit puzzled, I did not realize OpenRefine depended on rhino directly. Our web framework "butterfly" does rely on it (depending on And it seems to run fine without it. Really puzzling. Anyway, I do not understand modular compilation as well as you, but I do not think modular compilation is the source of the problem here: what is blocking is the "illegal reflexive accesses" that we have been warned about for a long time now. Upgrading Butterfly's dependency to Rhino to the latest release candidate does solve the problem. |
That's good to know :-) There is a pending PR with reflective access fixes (related to issues with protected fields and methods) which may be included in the final Rhino 1.7.14. |
* Updated build-test-run.md no JDK later that 14.0.2 Added a recommendation about JDK version to use. Build-test-run.md sugguested to install the latest JDK which let's you build OpenRefine, but running it does not work see: #4106 This might be frustrating for beginners not aware of this issue. * Update build-test-run.md changed Java version recommendation according to disucussion on #4280 Co-authored-by: Antonin Delpeuch <antonin@delpeuch.eu>
@nikhilp3 may I ask why you unpinned this? |
Sorry @wetneb must've been on accident |
* Migrate to log4j 2.16.0 * Bump to Butterfly 1.2.2 for Rhino upgrade (#4106) * Re-add log4j as dependency of the main module for tests
* Migrate to log4j 2.16.0 * Bump to Butterfly 1.2.2 for Rhino upgrade (#4106) * Re-add log4j as dependency of the main module for tests
To Reproduce
Steps to reproduce the behavior:
Current Results
4. This page appears
5.
6.I have installed the embedded Java version:
7.I have run it as adminstrator same results.
Expected Behavior
Open Refine page appears
Screenshots
Versions
Operating System: Edition Windows 10 Pro
Version 20H2
Installed on 17/03/2021
OS build 19042.1165
Experience Windows Feature Experience Pack 120.2212.3530.0
Browser Version:
JRE or JDK Version:
Using embedded but:
Datasets
Additional context
The text was updated successfully, but these errors were encountered: