Page History

...

As a result Wicket upgraded its dependency of Spring Framework to 6.x which also led to requirement to use Java 17 for building and running Wicket applications.

Automatic migration

Add migration recipes to Wicket 10 WICKET-7029

Apache Wicket 10 provides automatic migration based on OpenRewrite.

Usage:

mvn -U org.openrewrite.maven:rewrite-maven-plugin:run -Drewrite.recipeArtifactCoordinates=org.apache.wicket:wicket-migration:LATEST -DactiveRecipes=org.apache.wicket.BestPractices

TODO

Use stable version of Commons FileUpload FILEUPLOAD-309

Re-enable cdi-unit tests once there is a new release cdi-unit#195

Changes

WicketTester and related classes have been extracted to wicket-tester Maven module WICKET-7072

TL;DR: Add org.apache.wicket:wicket-tester as a test dependency to your project and fix the imports in your project.

Until now WicketTester class was a member of the wicket-core module. But it depends on JUnit to do its job and this caused problems in JPMS (Java 9+ modules) because JPMS does not support optional dependencies like Maven/Gradle do. For this reason WicketTester and the other **Tester classes have been extracted to a new Maven/JPMS module - wicket-tester. Same is valid for WebSocketTester - it has been moved to wicket-web-socket-tester module,

wicket-http2 module have been merged to wicket-core module WICKET-6887

...

Spring Framework to 6.x WICKET-6940

Guice to

...

7.x

Upgrade Guice to 57.0.1 0 WICKET-69077053

Commons Fileupload to 2.x WICKET-6915

...