You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2021/08/06 01:00:17 UTC

[jira] [Commented] (WICKET-6913) Java 17 compatibility

    [ https://issues.apache.org/jira/browse/WICKET-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394408#comment-17394408 ] 

Maxim Solodovnik commented on WICKET-6913:
------------------------------------------

AFAIK wicket-10 Java17 builds are green https://ci.apache.org/builders/wicket-10.x-java17 (except for some JavaDoc issues ...)

> 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)