[
https://issues.apache.org/jira/browse/WICKET-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Bain updated WICKET-6913:
--------------------------------
Description:
Wicket's use of cglib means that as of Java 16, you need to specify
--illegal-access=permit. As of Java 17, this is no longer possible, which I've
verified using a JDK 17 Early-Access Build.
See [https://github.com/cglib/cglib/issues/191]
See
[https://stackoverflow.com/questions/66974846/java-lang-exceptionininitializererror-with-java-16-j-l-classformaterror-access]
was:
Wicket's use of cglib means that as of Java 16, you need to specify
--illegal-access=permit. As of Java 17, this is no longer possible, which I've
verified using a JDK 17 Early-Access Build.
See [https://github.com/cglib/cglib/issues/191]
> Java 17 compatibility
> ---------------------
>
> Key: WICKET-6913
> URL: https://issues.apache.org/jira/browse/WICKET-6913
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
> Affects Versions: 9.4.0
> Reporter: Robert Bain
> Priority: Major
>
> Wicket's use of cglib means that as of Java 16, you need to specify
> --illegal-access=permit. As of Java 17, this is no longer possible, which
> I've verified using a JDK 17 Early-Access Build.
> See [https://github.com/cglib/cglib/issues/191]
> See
> [https://stackoverflow.com/questions/66974846/java-lang-exceptionininitializererror-with-java-16-j-l-classformaterror-access]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
