-
Notifications
You must be signed in to change notification settings - Fork 143
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
Investigate adopting Java SE 11 features #285
Comments
Java_11_features#285.txt |
So basically no readily identifiable changes for us? |
Yes, It seems there are no apparent changes for us. right now |
OK. I’ll leave this open for a little bit and then close it if it stays inactive. |
Sure, this sounds good. |
Will need an equivalent issue for Java SE 17 soon, specifically for Records. |
Shall we close this or rename it? |
If you have time, you should investigate. I have not had time to verify myself that there really isn't anything. We can't really adopt SE 17 before we adopt EE 11. |
The Jakarta EE 10 baseline is Java SE 11, so we can now consider adopting it in the application and no longer need to stick to Java SE 8. However, I don't see any obvious features to adopt in the application: https://www.baeldung.com/java-11-new-features. Others should investigate if there are such reasonable opportunities.
The text was updated successfully, but these errors were encountered: