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

Use Java 11 #707

Merged
merged 1 commit into from Mar 13, 2023
Merged

Use Java 11 #707

merged 1 commit into from Mar 13, 2023

Conversation

mickaelistria
Copy link
Contributor

@mickaelistria mickaelistria commented Mar 13, 2023

Fixes #547

@eclipse-lsp4j-bot
Copy link

Can one of the admins verify this patch?

@cdietrich
Copy link
Contributor

@eclipse-lsp4j-bot run tests

@jonahgraham
Copy link
Contributor

Note that this change needs CI updates too as CI uses Java 8.

@cdietrich
Copy link
Contributor

@eclipse-lsp4j-bot run tests

@jonahgraham
Copy link
Contributor

@eclipse-lsp4j-bot run tests

That won't work as the PR job doesn't use Jenkinsfile. Landing #706 first may help here.

@cdietrich
Copy link
Contributor

@jonahgraham as our pr build do this "run on top thing"
is there any way to test this besides pushing it as real branch?

@cdietrich
Copy link
Contributor

@jonahgraham
Copy link
Contributor

pushed to https://ci.eclipse.org/lsp4j/job/lsp4j-multi-build/job/mickaelistria-java-11/

That is a good solution. Alternatively change the JDK in the PR job now.

@@ -7,7 +7,7 @@ pipeline {
}
tools {
maven 'apache-maven-latest'
jdk 'oracle-jdk8-latest'
Copy link
Contributor

Choose a reason for hiding this comment

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

can you also adapt the 2nd jenkinsfile

@cdietrich
Copy link
Contributor

@cdietrich cdietrich added this to the 0.21.0 milestone Mar 13, 2023
@szarnekow
Copy link

No description provided.

@mickaelistria can you please explain the problem you're going to solve here from an lsp4j maintainers point of view? If I understand it correctly, this change will only make the next release incompatible to Java8 without any other user observable modifications?

@mickaelistria
Copy link
Contributor Author

On #705 , I was encouraged to switch to Java 11 by @jonahgraham who referred to #547 . Supporting less versions is naturally reducing the target/scope of the project and thus reducing the amount of combination that are supposedly supported, thus decreasing the support cost; moving to newer versions enables to use newer feature languages which are most often more powerful or less error-prone, allow to keep the code more modern and more appealing to new contributors.
The real question is not "why" but "why not"? Is anyone in LSP4J committer really gaining anything with Java 8 support? If there is no value generated by this constraint, why not getting rid of it?

@jonahgraham
Copy link
Contributor

@eclipse-lsp4j-bot run tests

@szarnekow
Copy link

@mickaelistria A link in the commit message would have rendered my question obsolete, I guess.

@jonahgraham
Copy link
Contributor

@mickaelistria A link in the commit message would have rendered my question obsolete, I guess.

I added the missing "Fixes..."

Copy link
Contributor

@jonahgraham jonahgraham left a comment

Choose a reason for hiding this comment

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

Needs changelog entry.

I am making the remaining changes now, so no need for more updates

@@ -7,7 +7,7 @@ pipeline {
}
tools {
maven 'apache-maven-latest'
jdk 'oracle-jdk8-latest'
jdk 'openjdk-jdk11-latest'
Copy link
Contributor

Choose a reason for hiding this comment

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

openjdk latest is not a good idea, it is not kept up to date. Use adopt instead.

Copy link
Contributor

Choose a reason for hiding this comment

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

You mean temurin? :)

Copy link
Contributor

Choose a reason for hiding this comment

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

yes temurin-jdk11-latest

@jonahgraham
Copy link
Contributor

@eclipse-lsp4j-bot run tests

@jonahgraham jonahgraham merged commit a491eec into eclipse-lsp4j:main Mar 13, 2023
@ice1000
Copy link

ice1000 commented Mar 13, 2023

Coool!!

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.

Migrate to Java 11
7 participants