The Future of Liferay & Java and How It Affects Liferay

Note: This article was last updated on August 14, 2025, to ensure all information is up-to-date.

Key Takeaways

• Java is the foundation of Liferay DXP, and the platform’s Java roadmap closely follows Java’s evolution to maintain compatibility, security, and performance.

• Current focus: Java 17 and Java 21 are the main LTS versions supported, with Java 21 becoming the primary runtime in 2026.

• Major update: Liferay DXP will adopt Jakarta EE 10 in Q3 2025, requiring updates to any custom code deployed inside DXP.

• Release cadence: Java feature releases arrive twice a year; LTS versions get multi-year support. Liferay’s LTS releases include 3 years of Premium Support + 2 years of Limited Support.

• Java 8 is effectively end-of-life for public updates; upgrading to Java 17 or Java 21 is strongly recommended.

• Development best practice: Always build and test against the latest supported Java versions, review compatibility matrices, and use Liferay tools like Blade CLI, Liferay IDE, and Gradle plugins.

Keeping Pace with Java’s Evolution

If you’ve been around the Java world for a while, you’ve lived through a decade of big changes – from the introduction of the six-month release cadence to the evolution of the LTS model, from the sunset of Java 8 public updates to today’s push toward Java 21 and beyond. Through it all, Java has remained the backbone of Liferay DXP, and that’s not changing anytime soon. Liferay Portal, originally developed over a decade ago, continues to be actively developed to keep pace with industry changes. As industry-wide shifts in Java standards and technologies occur, Liferay Portal adapts to ensure compatibility across different Java versions, application servers, and API standards like Jakarta EE, facilitating ongoing compatibility and innovation. Liferay’s roadmap includes a focus on Java 21 as the main runtime version starting in 2026.

Liferay’s Java roadmap continues to track closely with the language’s evolution, ensuring that developers can build secure, high-performing solutions without worrying about falling behind on compatibility. Liferay’s Java roadmap is designed to align with the next generation of Java, supporting future advancements and migration strategies.

Java’s Ongoing Role in Liferay

Java isn’t just a technical requirement for Liferay DXP – it’s the foundation. Compatibility between the Java JDK and Liferay DXP is critical to performance, security, and stability.

Today, Liferay DXP runs on Java LTS release versions, with Java 17 and Java 21 as the main focus for new projects. In 2025, Liferay will compile DXP on Java 17 to ensure broad compatibility, while maintaining runtime support for both Java 17 and Java 21. This means there may be a temporary mismatch between the compile version (17) and the recommended runtime (21). Java 21 offers improved performance, enhanced security, and cost-saving features—making it the preferred choice for deployments even during this transition period.

Liferay’s developer workspace – Gradle, Blade CLI, and IDE plugins – already supports building custom modules with Java 17 and Java 21, giving teams the flexibility to target their preferred LTS version. This tooling will continue to evolve alongside our Java migration, ensuring developers can adopt new features without breaking compatibility.

Once the Jakarta EE 10 migration and application server upgrades are completed in Q3 2025, Liferay will turn its attention to the final goal: becoming a full Java 21 enterprise platform. At that point, Java 17 will be deprecated, with a planned shift to Java 21 for both compile and runtime in 2026.

If you’re deploying custom code inside Liferay DXP, staying aligned with the latest LTS releases is essential. Application servers like Apache Tomcat and WildFly, which host Liferay instances, also require updated Java support. Even client extension customizations running outside the Liferay JVM can be affected by Java changes, though these are managed separately from in-VM deployments, allowing for smoother upgrades and migrations.

The migration to Jakarta EE 10 will require updates to any custom code deployed inside DXP, so now is the time to review and prepare your codebase.

Liferay DXP Today

Liferay DXP is an enterprise-grade digital experience system built to create, manage, and optimize digital experiences across web, mobile, and beyond – all from one secure, unified environment. It offers comprehensive functionality and all the flexibility organizations need to create the exact solutions they want.

• Built on Java: Ensures enterprise-grade reliability and compatibility.

• Composable architecture: Supports multi-site and multi-audience needs with reusable content, templates, and workflows. Each module serves as a building block, and modules and templates can be easily configured to meet specific business requirements.

• Flexible deployment: Liferay’s available subscription options – SaaS, PaaS, and On-Premise/your own cloud – allowing organizations to adapt the system to their diverse business needs.

• Enterprise integration framework: Open API and connectors to integrate with core systems like CRM, ERP, and identity management, streamlining connectivity and data flow. Liferay DXP can also integrate with external databases and file storage systems to enhance content management and data accessibility.

• Scalable and secure: Meets the demands of mission-critical applications with built-in governance, access control, and high availability.

• Comprehensive capabilities: Delivers robust out-of-the-box capabilities like content management, AI, low-code, commerce, digital asset management, personalization, or integration.

Users can interact with the system’s features through intuitive interfaces, manage content, participate in workflows, and customize their experience using available settings. Tools are provided to facilitate content creation, management, and workflow optimization. Analytics tools in Liferay DXP help track user behavior and engagement with content such as articles, blog posts, and files. Administrators can set various configuration options and page settings, ensuring each setting is tailored to the platform’s requirements. Whether starting a new project or enhancing an existing one, Liferay DXP provides the flexibility and ability to meet evolving business demands.

By staying aligned with Java’s release cycle, Liferay DXP makes it easier for organizations to keep their environments modern, secure, and ready for what’s next.

The Release Cadence – Still Going Strong

Back in 2017, Oracle introduced a faster Java release cadence: a feature release every six months (March and September) and designated LTS (Long-Term Support) versions every few years. That shift – once a big adjustment – is now the norm. Liferay’s Long-Term Support (LTS) versions will be designated as having a three-year Premium Support Phase followed by a two-year Limited Support Phase.

Here’s what that means in 2025:

• Feature releases: Arrive twice a year, supported for six months. Be sure to track the specific support dates for each release.

• LTS versions: Get multi-year support from vendors and are the recommended baseline for production environments. For more details on support periods, consult your vendor’s documentation.

• OpenJDK as default: There’s now no functional difference between Oracle JDK and OpenJDK; the latter is the go-to for most developers.

Note: Oracle provides free updates for the first six months of any release, after which you’ll need a paid subscription for Oracle JDK updates. The good news? Other vendors – like Red Hat, IBM, Azul, and community projects – continue to provide extended support for LTS releases.

The bottom line: keep an eye on support timelines and plan migrations early to avoid security or compatibility gaps. Make sure to complete your migration before support end dates to ensure continued functionality and support. When adopting new Java or Liferay releases, always follow proper install procedures – including downloading, configuring, and starting the server or application – to ensure a smooth and reliable setup.

Overview: Cadence Details and Support Phases

Where Are We Now with Java 8?

The beginning of the end-of-life process for Java 8 started when Oracle ended its public updates back in 2019. Red Hat then led community maintenance for years after that, with backing from vendors like Amazon, Azul, and IBM. But by 2025, most published public updates have ended.

If you’re still on Java 8, you’re likely relying on paid commercial support – and you’re overdue for an upgrade. Upgrading to the latest version ensures you benefit from improved performance, the newest features, and enhanced security.

Overview: Key Java Versions, Support Timelines, Recommended Actions

Development Tools and Best Practices

Staying current with Liferay’s Java roadmap is essential for any development team looking to build robust, future-proof solutions on the Liferay platform. As new versions of Java JDK are released, ensuring compatibility between your custom code, the Liferay JVM, and the application servers you deploy on becomes a top priority. This alignment not only guarantees seamless integration but also maximizes performance, security, and long-term support for your projects.

1. When developing for Liferay, always verify that your custom code is built and tested against the latest supported Java versions. This proactive approach helps avoid unexpected issues during upgrades and ensures your solutions take full advantage of new features and security enhancements. It’s also important to regularly review the compatibility matrix for both Liferay DXP and your chosen application servers, as support for specific Java versions can vary between platforms. As of now, Liferay plans to use Java 17 as the compiler while maintaining runtime compatibility with Java 21.

2. To streamline the development process, Liferay offers a suite of powerful tools designed to boost productivity and simplify complex tasks. The Liferay IDE provides a familiar, Eclipse-based environment tailored for portal development, while Blade CLI offers a command-line interface for creating, managing, and deploying modules with ease. Gradle plugins further enhance your build process, enabling you to automate tasks and maintain consistency across different environments.

By leveraging these tools and following best practices for version management and compatibility, developers can confidently create, modify, and maintain custom code that integrates smoothly with the latest versions of Liferay DXP. It is crucial to test and deploy new app versions to ensure compatibility with the latest Java and Liferay releases, as this supports improved security, performance, and alignment with current standards. This approach not only reduces technical debt but also positions your organization to quickly adopt new technologies and features as they become available, ensuring your Liferay solutions remain flexible, secure, and ready for the future.

Wrapping It Up

Java’s faster release cycle is here to stay, and Liferay is keeping pace. By aligning Liferay DXP as a solution for enterprise needs with the latest LTS versions – and adopting Jakarta EE 10 this year – we’re making sure you can innovate without worrying about whether the foundation will hold.

Liferay continues to support its customers through regular updates, enhancements, and a commitment to seamless migrations. These updates help clients stay secure and competitive in a rapidly changing technology landscape. The team is prepared to respond quickly to changes in the Java ecosystem and evolving customer needs.

If you want to dig deeper, the community-maintained document Java Is Still Free is still the best resource for up-to-date information on Java’s licensing, support, and roadmap.

As always, Liferay will keep updating its JDK compatibility support in step with Java’s evolution, so you can plan your upgrades with confidence – and keep building experiences that are ready for the future.