Migration to Wicket 9.0

Environment

Wicket 9.0 requires Java 11

Removals

Removed from wicket-core all the deprecated classes Unable to render Jira issues macro, execution error.

Several deprecated classes were removed from wicket-core:

• org/apache/wicket/RequestListenerInterface.java

• org/apache/wicket/markup/IMarkup.java

• org/apache/wicket/model/AbstractReadOnlyModel.java

• org/apache/wicket/model/IChainingModel.java

• org/apache/wicket/protocol/http/documentvalidation/Comment.java

• org/apache/wicket/protocol/http/documentvalidation/DocumentElement.java

• org/apache/wicket/protocol/http/documentvalidation/HtmlDocumentParser.java

• org/apache/wicket/protocol/http/documentvalidation/HtmlDocumentValidator.java

• org/apache/wicket/protocol/http/documentvalidation/Tag.java

• org/apache/wicket/protocol/http/documentvalidation/TextContent.java

• org/apache/wicket/request/cycle/AbstractRequestCycleListener.java

Upgrades

Upgrade JUnit to version 5  Unable to render Jira issues macro, execution error.

All **Tester classes (e.g. WicketTester, FormTester, TagTester, WebSocketTester) now depend on JUnit 5.x instead of 4.x.

Update CDI integration to CDI 2.0 specification  Unable to render Jira issues macro, execution error.

The old wicket-cdi  module based on CDI 1.0  has been replaced with wicket-cdi-1.1 module (based on CDI 1.1), which has been updated to CDI 2.0. No code change or API break  has been required for this update, hence those who were using wicket-cdi-1.1 should have no problem migrating to the new wicket-cdi  module.

Use JQuery 3.x by default  Unable to render Jira issues macro, execution error.

JQuery 2.x is not maintained anymore by jQuery team. Wicket will use by default latest available 3.x version.

Dependency updates

All libraries on which Wicket modules depend are updated to their latest stable versions.
The most notable ones are:

• Spring Framework 5.x
• Objenesis 3.x