[
https://issues.apache.org/jira/browse/WICKET-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205556#comment-17205556
]
Gert-Jan Schouten commented on WICKET-6836:
-------------------------------------------
I think so too, I'll confirm when the patch is available on the Maven Central.
Now that we're talking about dependencies: I see that wicket-util has a
compile-time dependency on junit-jupiter-engine. This is explicitly done in the
wicket-util pom.xml. Is that the right thing to do? Because it means that the
entire jupiter test engine is automatically included in my war file. I could
exclude it, but I'm not sure if wicket-util needs it somewhere. And if it's
only needed for test utilities, then shouldn't they be in a separate jar file,
wicket-test-util?
Sorry for this unrelated question, but I don't want to submit a new issue when
I'm not sure it's an issue at all.
> Replace CGLib with ByteBuddy and/or Javassist
> ---------------------------------------------
>
> Key: WICKET-6836
> URL: https://issues.apache.org/jira/browse/WICKET-6836
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-ioc
> Affects Versions: 9.0.0
> Environment: Linux
> Reporter: Gert-Jan Schouten
> Priority: Minor
>
> When trying to run Wicket 9.0.0 under Java 15, it fails with an "Unsupported
> class file major version 59" error from CGLib.
> [This issue|https://github.com/cglib/cglib/issues/74] suggests that CGLib is
> not actively maintained anymore. The Maven Central hasn't seen a new version
> since August 2019.
> To make sure Wicket keeps running on the latest Java version, a migration to
> ByteBuddy and/or Javassist is recommended.
> This is especially relevant since Oracle now only supports the latest version
> of OpenJDK, requiring OpenJDK users to switch to the latest version every 6
> months.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
