Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Drop Java 8 #793

Merged
merged 2 commits into from
Sep 29, 2022
Merged

Drop Java 8 #793

merged 2 commits into from
Sep 29, 2022

Conversation

mkurz
Copy link
Member

@mkurz mkurz commented Sep 29, 2022

No description provided.

@mkurz mkurz merged commit a907033 into playframework:main Sep 29, 2022
@mkurz mkurz deleted the dropJava8 branch October 5, 2022 09:10
@cchantep
Copy link
Member

Hi,

Play-JSON 2.10.0 has just been published, I would have been pleased to upgrade to ... but as working a app that must run on Java 8 ...

We can considered that we have to upgrade ... JVM is a system component, and in some context it's not as easy ... compared to the fact that it has no cost for the Play JSON build ...

@mkurz
Copy link
Member Author

mkurz commented Sep 18, 2023

@cchantep Hmm... I think it's time to move on at some point? Java 8 was released almost 10 years ago. Some libraries started to drop Java 8 artifacts. Bigger frameworks like Spring, with version 6, even require Java 17 (!) already...
I do understand that there will always be organziations which follow a very conservative approach of upgrading software components, but at some point we have to make a cut IMHO.
Is it that hard for you/your organzation to upgrade to Java 11/Java 17? Like are you using some special Java 8 flags/workarounds etc.? Or is it "just" a matter of manpower, time and testing to perform a Java upgrade?

@cchantep
Copy link
Member

"Or is it "just" a matter of manpower, time and testing to perform a Java upgrade?" your argument can easily to reverted ... as the Java8 compatibility has no cost there.

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

Successfully merging this pull request may close these issues.

2 participants