[
https://issues.apache.org/jira/browse/WICKET-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214218#comment-17214218
]
Sven Meier commented on WICKET-6832:
------------------------------------
Sorry guys, but the changes in WICKET-6703 can not be applied to Wicket 8.x,
due to breaking API changes.
And I doubt Wicket 8.x will be supported until 2026 :P.
IMHO it would be easier to make Wicket 9.x compatible with Java 8. Switched in
the pom here and got a bunch of these only:
* '<>' cannot be used with anonymous classes
* The method isBlank() is undefined for the type String
* The method toSeconds() from the type Duration is not visible
* The operator > is undefined for the argument type(s) BigDecimal
* The method canAccess(Object) is undefined for the type Field
> 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)
