Liferay DXP + JBoss EAP 8 Compatibility FAQ

When will Liferay Support JBoss EAP 8.0?

• Our team is actively working on making Liferay compatible with JBoss EAP 8. Upgrading to JBoss EAP 8 will require migrating to a newer version of Liferay DXP that supports Jakarta EE 10, which is planned for release in the second half of 2025 (2025.Q3) at the earliest.
  

• For additional documentation you can refer to: Liferay's Java Roadmap for 2025 - Liferay and Java & Liferay - 2025 and Beyond

How many of Liferay’s core modules are impacted by the migration?

• The transition to JBoss EAP 8, JDK 17, and particularly Jakarta EE 10 (required for JBoss EAP 8) will necessitate updates to the following:

  • Core modules in Liferay’s codebase.

  • Third-party libraries.

  • Frameworks such as OSGi, Portlet API, JSP, etc

  As part of the Liferay 2025.Q3 release, Liferay will:

  • Adjust its application to address deprecated methods.

  • Provide additional details about breaking changes

  Note: Currently, detailed information about which specific core modules will be impacted is not available. Updates will be shared closer to the 2025.Q3 release

Will we be able to upgrade to JBoss EAP 8.0 or will we need to set up a new infrastructure to deploy Liferay on?

• Existing client data will likely be able to be upgraded as part of Liferay’s upgrade process. You will need to review system requirements with respect to JBoss EAP 8 and should plan it into a different environment so that it does not affect your current setup. 

Is Liferay aware that support for JBoss 7 ends on June 30th, 2025?

• Yes, our team is aware that official support for JBoss 7.4 ends on June 30th, 2025. 

• Liferay started this project before the release of JBoss EAP 8. Migrating to JBoss EAP 8.0 is not just a standard application server upgrade; it involves significant architectural and compatibility changes. It required upgrading our base JDK version (which was completed last year) and now the move to Jakarta (which we will complete this year). We have needed to find ways to do these sweeping and fundamental changes to the codebase without completely stopping all other feature development.
  

• At the moment, customers will need to continue using EAP 7, and once the maintenance support ends, you will need to further keep using it until JBoss EAP 8 is officially supported. 

Are there any Beta Releases Planned before the actual release of Q3?

• The current timeline is tight, making even a Q3 release challenging, and the Product team is not confident in providing a beta release any earlier. 

Does Liferay recommend to upgrade to 2025.Q3 release as soon as possible?

• We recommend launching projects on Q1 LTS releases (e.g., 2026.Q1) for longer-term support unless Q2, Q3, or Q4 releases provide material value to your specific project with new capabilities and features important for you. In that case please take notice of 2025.Q3's shorter support window and plan for an upgrade to the next Q1 LTS release within 1 year.

How can we start preparing for the migration before the compatible Liferay version is released?

• Currently, the Product team is preparing documentation and guidelines. Since they are still finalizing the process with Liferay’s own codebase, they will have more to share in the future. For now, the client can review generally available public documentation about moving from JavaEE to Jakarta EE 10 since some of this is not specific to Liferay, but the Java ecosystem in general.

• The customer can work on updating their custom code to use Jakarta EE 10 packages instead of javax packages. Some useful tools are OpenRewite and Eclipse Transformer.

• This is a good time for customers to evaluate the feasibility of migrating customizations/custom code to Low Code or Client Extensions. Since February 11th, 2025, the Client Extensions framework is available for Liferay PaaS customers as a Beta feature.

Will Liferay provide documentation on how to migrate?

• Currently, the Product team is preparing documentation and guidelines on how to migrate effectively.

• You can stay informed by following our developer blogs and official announcement channels, where we’ll share the latest updates and insights regarding the Jakarta EE 10 migration.