With the upcoming release of Jakarta and new application server versions, Liferay is focused on becoming a full feature enterprise platform. Supporting Java 17 prevents usage of Java 21 features that will improve performance and reduce cloud costs. We are marking Java 17 for deprecation as we plan to fully focus on Java 21 in 2026.
Release Notes
We integrated the Clay Table's column visibility dropdown and column sorting functionalities into the Frontend Data Set. This makes a unified approach to table interactions across Liferay, replacing inconsistent custom implementations.
Key Benefits:
A more standard column visibility and sorting that guarantee a more usable and predictable interaction across the platform.
Reduces redundant code by aligning with the Clay Table’s native functionalities.
Developers no longer need to manage multiple implementations for similar features.
Ensures UI and UX consistency with Liferay’s design system.
Style Books in Liferay are now explicitly tied to a specific theme at the moment of creation, using the frontend token definition provided by that theme (via OSGi or themeCSS client extension). This structural link now ensures that each Style Book can only operate within the boundaries of its associated theme, eliminating cross-theme token contamination and enforcing clearer theme-based design governance.
Key Benefits:
Users can no longer save Style Books that accidentally combine tokens from different themes, avoiding visual inconsistencies and design regressions.
Every Style Book now visibly shows which theme it belongs to, reducing errors and making it easier for teams to manage design assets across multiple sites.
When applying a Style Book to a page, the system will only list those created with the same theme as the page’s current one—no more trial-and-error or guesswork.
If a Style Book becomes incompatible with the applied theme (e.g., after a theme change), it will be automatically unlinked to prevent display issues.
During platform upgrades, existing Style Books are automatically linked to the site’s current public theme (as defined in Site Builder > Pages > Options > Configuration), reducing manual cleanup work.
If a Style Book is imported without a valid
themeId
, the user gets a clear warning and knows exactly what’s missing to fix the import.Style Books based on themes that are no longer deployed or no longer provide a valid frontend token definition are automatically marked as inactive—clearly flagged and non-selectable.
The OSGi or themeCSS client extension ID is displayed for inactive Style Books, helping devs or admins identify which theme needs to be re-installed or fixed.
This release introduces a new Stripe Tax connector, now available in the Liferay Marketplace, designed to integrate directly with Liferay Commerce’s core transaction flows. This connector enables dynamic, automated tax calculation powered by Stripe Tax, replacing manual or static tax setups with an automated, accurate, and globally compliant solution.
Once installed and configured, the connector calculates taxes automatically at checkout based on the buyer’s shipping address and the seller’s tax registration settings. The integration is especially valuable for businesses operating in tax-complex regions like the United States, where tax rates and rules can vary dramatically between states, counties, and even cities.
By leveraging Stripe Tax through this connector, merchants benefit from seamless tax compliance, transparent pricing for buyers, and simplified tax reporting for administrators.
Key Benefits:
- Automated Real-Time Tax Calculation
Eliminate manual tax logic. Taxes are calculated dynamically during checkout using Stripe’s robust tax engine, ensuring accuracy based on product, location, and applicable tax laws. - Supports Complex U.S. Tax Scenarios
This is particularly beneficial for merchants selling into the U.S. market, where tax complexity is high. Stripe Tax automatically accounts for state, county, and city-level rules—reducing the burden on sellers. - Improved Buyer Experience
Buyers see clear tax breakdowns at checkout, building trust and preventing cart abandonment due to surprise charges. - Streamlined Operations for Sellers
Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.Streamlined Operations for Sellers
Taxes are included in transaction records without seller intervention. Sellers can access tax-inclusive transaction histories and focus on business growth.