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

make default jdk 11 #1387

Merged
merged 4 commits into from
Feb 22, 2022
Merged

Conversation

aleksandy
Copy link
Contributor

Since 6dabc53 play! is compiled and tested on jdk 11 and 17 in CI. So in my opinion it's good cause to migrate to jdk 11 in the next release.

@aleksandy
Copy link
Contributor Author

It looks like after a481dd3 there is no option to use java 8. Because eclipse.jdt.core was updated to 3.28.0 and starting from 3.27.0 it requires java 11.


Values: @1.7@ (No longer supported since 1.5.0), @1.8@, @9@, @10@, @11@, @12@, @13@, @14@, @15@, @17@.
Values: @1.7@ (No longer supported since 1.5.0), @1.8@ (No longer supported since 1.6.x), @9@ (No longer supported since 1.6.x), @10@ (No longer supported since 1.6.x), @11@, @12@, @13@, @14@, @15@, @17@.
Copy link
Member

Choose a reason for hiding this comment

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

I think that it should be 'No longer supported since 1.7.0' has the 1.6.0 still support java 8 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Only if it will be next release. Because code already is uncompilable with java 8.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@xael-fry xael-fry added this to the 1.7.0 milestone Feb 22, 2022
@xael-fry xael-fry merged commit 3bdf946 into playframework:master Feb 22, 2022
@xael-fry
Copy link
Member

Merged thanks @aleksandy

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

Successfully merging this pull request may close these issues.

3 participants