[
https://issues.apache.org/jira/browse/WICKET-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216697#comment-17216697
]
Emond Papegaaij commented on WICKET-6832:
-----------------------------------------
I totally agree with Martin, Sven and Andrea here. The fact that JDK 8 still
has support (read gets bug and security fixes), does not mean that a framework
like Wicket needs to put effort in supporting new features on this old JDK.
Wicket 8 probably will be supported (read gets bug and security fixes) for
several years to come. For new features, you will have to upgrade your entire
stack not just Wicket. The Wicket team has limited resources and we cannot
afford to spend it on supporting many different platforms.
There is nothing stopping you from forking the Wicket source code and either
backport the features you need from Wicket 9 to Wicket 8 or downgrade the Java
version in Wicket 9 though.
> CSP support in Java 8
> ---------------------
>
> Key: WICKET-6832
> URL: https://issues.apache.org/jira/browse/WICKET-6832
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 9.0.0, 8.9.0
> Reporter: Ashley Reed
> Priority: Major
>
> Wicket needs Content-Security-Policy support in Java 8 as it is it the most
> popular version of Java used in production. Wicket 9 has CSP support, but
> requires Java 11. Wicket 8 runs on Java 8, but has no CSP support. Need to
> either add Java 8 support to Wicket 9 or add CSP support to Wicket 8.
>
> Evidence that Java 8 is still very popular:
> [https://blog.newrelic.com/technology/state-of-java/]
> [https://www.jrebel.com/blog/2020-java-technology-report]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
