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

Require Java 11 #1048

Merged
merged 1 commit into from
Jan 10, 2025
Merged

Require Java 11 #1048

merged 1 commit into from
Jan 10, 2025

Conversation

datho7561
Copy link
Contributor

lemminx is moving to Java 11, so this PR ensures that a Java 11 JRE/JDK is used to run lemminx (or uses the binary if Java 11 is not installed).

This PR also updates the documentation to reflect the new Java 11 requirement.

It also updates the documentation related to instructions on setting up GraalVM for locally building the binary.

Copy link
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine overall. Just missing an update at

"markdownDescription": "Specifies the folder path to the JDK (8 or more recent) used to launch the XML Language Server if the Java server is being run.\nOn Windows, backslashes must be escaped, i.e.\n`\"xml.java.home\": \"C:\\\\Program Files\\\\Java\\\\jdk1.8.0_161\"`. For more information, please refer to [this document](command:xml.open.docs?%5B%7B%22page%22%3A%22Preferences%22%2C%22section%22%3A%22java-home%22%7D%5D).",

lemminx is moving to Java 11,
so this PR ensures that a Java 11 JRE/JDK is used to run lemminx
(or uses the binary if Java 11 is not installed).

This PR also updates the documentation to reflect the new Java 11
requirement.

It also updates the documentation related to instructions on setting up
GraalVM for locally building the binary.

Signed-off-by: David Thompson <[email protected]>
Copy link
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine for now.

I did run into some odd workflows where the binary gets used automatically when I tried supplying a < 11 Java version. Then when the binary failed (wasn't trusted and I didn't opt to trust it), it complained that the binary server failed and that there is no Java on the system. That last message is technically wrong because there was Java, just not a valid version 😜 .

@datho7561 datho7561 merged commit 53f04ba into redhat-developer:main Jan 10, 2025
1 check passed
@datho7561
Copy link
Contributor Author

#1049

@datho7561 datho7561 deleted the require-java-11 branch January 10, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants