-
Notifications
You must be signed in to change notification settings - Fork 64
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
Move from Java 11 to Java 17 #839
Comments
Note this:
This means that until |
Note that this also requires bumping gradle, our current gradle version (6.5) only supports up to Java 14 |
Noted. We have already done this successfully in another branch called
‘release’. Xtext 2.26.0 also uses Gradle 7.
On Sat, Jan 29, 2022 at 4:54 AM Clément Fournier ***@***.***> wrote:
Note that this also requires bumping gradle, our current gradle version
(6.5) only supports up to Java 14
—
Reply to this email directly, view it on GitHub
<#839 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEYD47D6P43V2CXT7Q5RQUTUYPPQXANCNFSM5LXNMOYA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
…--
Marten Lohstroh | Postdoctoral Researcher
University of California | 545Q Cory Hall
Berkeley, CA 94720 | +1 510 282 9135
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest LTS version of Java is version 17, and it comes with a number features (e.g., text blocks) that are of help for some of our code generators that are currently still written in Xtend. For that reason alone, it would be great if we could move to Java 17.
It looks like Java 17 support is being worked on in eclipse-xtext/xtext#1982. With the release of
v2.6.0
(apparently due on Jan 31), we should attempt to bump our Java dependency as well.The text was updated successfully, but these errors were encountered: