Skip to content
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

Scoreboard does not recognise OpenJDK JRE #785

Open
Tokoeka opened this issue Nov 5, 2024 · 3 comments
Open

Scoreboard does not recognise OpenJDK JRE #785

Tokoeka opened this issue Nov 5, 2024 · 3 comments

Comments

@Tokoeka
Copy link

Tokoeka commented Nov 5, 2024

Describe the bug
I have a version of the adoptium JDK installed which includes a JRE. However, every time I have tested, I cannot get the Derby Scoreboartd to run without also installing the Oracle JRE.

To Reproduce
Steps to reproduce the behavior:

  1. Uninstall Oracle JRE (or get a computer that does not have it installed)
  2. Install the Adoptium JRE/JDK ( https://adoptium.net/en-GB/temurin/releases/ )
  3. Try to run Derby Scoreboard
  4. Scoreboard pop-up window appears indicating there is an error and that you dont have Java installed

Expected behavior
Scoreboard would run provided a version of Java was installed that was greater than the minimum required Oracle version.

Screenshots
image

Version:
2023.3 & 2023.7

If this issue occurred on a computer, please complete the following information:

  • Windows 10 Pro N
  • firefox (though not applicable as scoreboard did not progress far enough)
@frank-weinberg
Copy link
Contributor

Apparently the windows loader does not recognize the specific JRE as sufficient but the output doesn't give any indication as to why. I don't have windows so have no way to debug this (or build a new loader).

@JeneralPain
Copy link
Contributor

@frank-weinberg - I'll see if I can replicate this on a windows VM I'll setup and make some sense of the error.

@JeneralPain JeneralPain self-assigned this Dec 8, 2024
@official-sounding
Copy link
Contributor

This appears to be a launch4j bug - basically, l4j looks only at the windows registry to find a Java install. You would probably need to update the vendored version of l4j and re-run the launch4j ant task to rebuild the windows runner. That appears to be a cross-platform operation - it relies on windres which is in GNU binutils.

Also the state of self-contained java packages is much improved from the early-00s, so something like self-contained packages might be a better replacement (with the potential bonus of also packaging the JRE with the app, avoiding whole classes of Java incompatibility issues, allowing adoption of modern Java features, etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants