[
https://issues.apache.org/jira/browse/ROL-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104258#comment-18104258
]
Matt Raible commented on ROL-2183:
----------------------------------
The implementation is up for review as a stacked set of pull requests, and it
lands on Jakarta EE 11 specifically:
* [PR #154|https://github.com/apache/roller/pull/154] - the javax to jakarta
migration: Java 17 baseline, Servlet 6.1, Struts 7.1.1, Spring Framework 7.0.8,
Spring Security 7.0.6, EclipseLink 5.0.1, Jetty 12.1, Tomcat 11
* [PR #155|https://github.com/apache/roller/pull/155] - replaces the obsolete
OpenID 2.0 login with OAuth 2.0/OIDC via {{spring-security-oauth2-client}},
with Keycloak in docker-compose for local testing
* [PR #156|https://github.com/apache/roller/pull/156] - converts the admin and
editor UI from Bootstrap 3 to Bootstrap 5.3
* [PR #157|https://github.com/apache/roller/pull/157] - replaces it-selenium
with Playwright tests that run against db, oidc, and db-oidc auth in CI
A few notes on scope:
* The target started as EE 10 and moved to EE 11 during review, since Spring
Framework 7 is only supported on the Servlet 6.1 baseline.
* OAuth 1.0a and OpenID 2.0 are removed. Both protocols are obsolete and their
libraries are unmaintained and javax-only. The Blogger/MetaWeblog XML-RPC and
AtomPub APIs survive via servlets forked into Roller, now covered by smoke
tests.
* CI runs the build on JDK 17, 21, and 25, plus browser tests across the three
auth modes.
Review happens bottom up: #154 first, then the stack merges in order.
> Migrate from javax to jakarta namespace (Jakarta EE 9+)
> -------------------------------------------------------
>
> Key: ROL-2183
> URL: https://issues.apache.org/jira/browse/ROL-2183
> Project: Apache Roller
> Issue Type: Improvement
> Reporter: Matt Raible
> Assignee: Matt Raible
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Roller currently uses Java EE 8 APIs with the {{javax.\*}} namespace (Servlet
> API 4.0.1, JavaMail, JSP, JAXB, javax.activation). The JPA layer has been
> partially migrated to {{jakarta.persistence}}, but the rest of the codebase
> remains on {{javax.\*}}.
> This issue tracks the full migration to the {{jakarta.\*}} namespace to
> support Jakarta EE 9+ and modern servlet containers like Tomcat 10+.
> *Scope of changes:*
> * \~305 {{javax.\*}} imports across the codebase (servlet, JSP, mail,
> activation, XML bind)
> * \~31 {{jakarta.persistence}} imports already in place (JPA managers)
> * Servlet API dependency: {{javax.servlet:javax.servlet-api:4.0.1}} ->
> {{jakarta.servlet:jakarta.servlet-api:5.0+}}
> * JavaMail: {{javax.mail}} -> {{jakarta.mail}}
> * JSP: {{javax.servlet.jsp}} -> {{jakarta.servlet.jsp}}
> * JAXB: {{javax.xml.bind}} -> {{jakarta.xml.bind}}
> * {{javax.activation}} -> {{jakarta.activation}}
> * Update {{web.xml}} and any deployment descriptors
> * Update third-party dependencies to Jakarta-compatible versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)