[
https://issues.apache.org/jira/browse/WICKET-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197177#comment-17197177
]
Martin Tzvetanov Grigorov commented on WICKET-6723:
---------------------------------------------------
Actually there is no real need to move to jakarta.** APIs even if deploying on
EE 9 container.
One can use [https://github.com/apache/tomcat-jakartaee-migration] to migrate
his application. It migrates binaries, i.e. jar/war, so one can add an extra
step to the CI task!
I use the wicket-examples.war from Wicket master (i.e. 9.0.x) to test Tomcat
10.x releases each month.
> Move to Jakarta APIs and Servlet 4.0
> ------------------------------------
>
> Key: WICKET-6723
> URL: https://issues.apache.org/jira/browse/WICKET-6723
> Project: Wicket
> Issue Type: Task
> Components: wicket-core
> Affects Versions: 9.0.0-M4
> Reporter: Emond Papegaaij
> Assignee: Emond Papegaaij
> Priority: Major
>
> Wicket still uses javax GAVs for all Java EE APIs. These are now migrated to
> Jakarta and new artifacts have been published. This also requires the move to
> servlet 4.0.
> The following changes are required:
> * {{javax.el:javax.el-api}} -> {{jakarta.el:jakarta.el-api}}
> * {{javax.servlet:javax.servlet-api}} ->
> {{jakarta.servlet:jakarta.servlet-api}}
> * {{javax.servlet.jsp:javax.servlet.jsp-api}} ->
> {{jakarta.servlet.jakarta.servlet.jsp-api}}
> * {{javax.validation:validation-api}} ->
> {{jakarta.validation:jakarta.validation-api}}
> * {{javax.websocket:javax.websocket-api}} ->
> {{jakarta.websocket:jakarta.websocket-api}}
> * {{javax.enterprise:cdi-api}} ->
> {{jakarta.enterprise:jakarta.enterprise.cdi-api}}
> * {{javax.annotation:javax.annotation-api}} ->
> {{jakarta.annotation:jakarta.annotation-api}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
