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

End of first-class JDK 6 support [SPR-16185] #20733

Closed
spring-issuemaster opened this Issue Nov 10, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

spring-issuemaster commented Nov 10, 2017

Juergen Hoeller opened SPR-16185 and commented

As indicated by #20731, JDK 6 is severely outdated and effectively unmaintained in the meantime. The official end of of commercial JDK 6 support is coming up soon, with Oracle (http://www.oracle.com/technetwork/java/eol-135779.html) as well as IBM (https://developer.ibm.com/wasdev/docs/end-java-se-6-go/).

We'll have to join the club there, simply documentating that Spring Framework 4.3.x users are expected to be on recent patch releases of JDK 7, 8 or 9 these days. Let's roll this into 4.3.13's documentation and also blog about it around that time, officially declaring the end of first-class JDK 6 support on our end.

To be clear, we'll keep tolerating JDK 6 at runtime in the entire Spring Framework 4.3.x line, even in upcoming maintenance releases for the next few years. We just won't test on JDK 6 ourselves anymore and won't work around any JDK 6 specific issues, asking people to upgrade to JDK 7+ instead.


Issue Links:

  • #19713 Upgrade to CGLIB 3.2.5
  • #20159 Upgrade to Objenesis 2.6 for Google App Engine Standard on Java 8 and for better JDK 9 support
  • #20731 SettableListenableFuture set has a race on Java6 (and old versions of Java7)

Referenced from: commits ffbaa26

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

spring-issuemaster commented Nov 14, 2017

Juergen Hoeller commented

Note added to 4.3.13 documentation. Blog post following next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment