The official AWS SDK for Java 1.x went End-of-Life on 12/31/2025. The AWS SDK for Java 2.0 is the actively maintained solution for connecting to AWS with our Java platform. We have migrated our Amazon AWS S3 store connector to use SDK for Java version 2.0.

Breaking Changes:

1. NTLM Proxy Users: NTLM proxy authentication to connect to AWS will no longer work. Users will need to switch to username/password authentication or use another proxy solution.

2. Custom Signer Override: If you relied on signerOverride for compatibility with older S3-compatible services, you'll need to verify compatibility with SDK v2's default signing behavior.

3. Explicit HTTP Protocol: If you were forcing HTTP (non-HTTPS) connections via connectionProtocol, this setting is now ignored. The SDK will determine protocol based on your endpoint configuration.

4. In Summary, the following configuration keys are now for IBM only, they are no longer used by AWS

   1. signerOverride

   2. connectionProtocol

   3. ntlmProxyDomain

   4. ntlmProxyWorkstation

No new configuration keys added for AWS SDK v2 and Liferay still uses a single S3 configuration for both IBM S3 store and AWS S3 store.

In Previous releases, legacy data and module cleanup actions were triggered from configurations in System Settings > Upgrades > Data Cleanup (or Data Removal). These actions are important to improve performance, and improve long term system stability, and lighten the load during a DXP upgrade. We have brought some additional clarity and visibility to these system maintenance actions by moving them to Server Administration.

These can now be executed manually and on-demand from Control Panel → Server Administration → Resources → System Cleanup Actions (or Module Cleanup Actions). The names and tooltips for each of these have been updated to provide additional information on what each action does.

The following configuration files for these have been removed in favor of the Server Administration experience.

1. com.liferay.data.cleanup.internal.configuration.DataCleanupConfiguration.config

2. com.liferay.data.cleanup.internal.configuration.DataRemovalConfiguration.config

Based on feedback from our users, we have made some changes to the default behavior of the Database Upgrade Tool to improve usability and performance of the upgrade process.

1. The default maximum heap memory has been doubled from 2048 MB to 4096 MB. The previous default was insufficient for any large upgrades and could cause out-of-memory errors. The new default provides additional headroom and improves upgrade stability.

   1. Custom memory limits can still be set using the --jvm-opts parameter.

   2. Even larger limits may be needed depending on the database size.

2. Recent DXP versions ship with a simpler tomcat directory name instead of including the version number (such as tomcat-10.1.43). This applies to both bundled Tomcat releases and Docker images. The default in app-server.properties has been updated to match this change. This reduces the need for manual property management when upgrading modern DXP installations.

3. The interactive setup now validates inputs as they are entered, catching problems before the upgrade starts. Previously, only the application server type and database type were validated, allowing invalid values to proceed until failures occurred later in the process. This approach catches configuration mistakes early instead of allowing them to cause failures during upgrade execution. The following inputs are now validated:

   1. Directory paths: When paths are entered for Liferay home, application server directory, extra libraries, global library, or portal directory, the tool verifies they exist. Invalid paths trigger an error message explaining the issue, and the prompt repeats.

   2. Database host: The tool checks if the database hostname can be resolved via DNS. Resolution failures result in an error message with details.

   3. Database port: Port numbers are validated to ensure they fall within the valid range (0-65535). Invalid ports are rejected immediately with an error.

4. The tool now reads existing database configuration from portal-ext.properties instead of requiring re-entry. It can still be overridden by portal-upgrade-ext.properties.

5. Default JVM parameters are automatically applied, in addition to custom parameters from --jvm-opts. The following are applied unless explicitly changed by the user:

   1. -Dfile.encoding=UTF8

   2. -Duser.country=US

   3. -Duser.language=en

   4. -Duser.timezone=GMT

   5. -Xmx4096m

6. To improve database upgrade performance, database connections are now automatically configured with batch insert optimization parameters, removing the need for manual JDBC URL configuration for the upgrade. User defined parameters are still preserved.

   1. PostgreSQL: Adds reWriteBatchedInserts=true to enable batch insert optimization

   2. MySQL/MariaDB: Adds rewriteBatchedStatements=true to enable batch statement rewriting

   3. SQL Server: Adds useBulkCopyForBatchInsert=true to enable bulk copy for batch operation

7. The upgrade tool now uses a single configuration file for all upgrade settings. All properties are set from portal-upgrade-ext.properties. The portal-upgrade-database.properties is now deprecated and ignored.

8. The default application server directory paths in both the app-server.properties template have been updated to use explicit relative path notation to reduce confusion about the upgrade file paths.

   1. /bin → ./bin

   2. /lib → ./lib

   3. /webapps/ROOT → ./webapps/ROOT

   4. /WEB-INF/... → ./WEB-INF/...

9. The upgrade tool's interactive wizard now uses PostgreSQL as the default database. This change reflects PostgreSQL's widespread adoption and recommended usage for Liferay DXP. Users can still select any supported database by entering a different value at the prompt.

The following features will be removed in the upcoming Liferay Developer Studio (LDS) release:

• Liferay Upgrade Planner: Feature to aid developers in migrating their code from older versions of Liferay to newer versions.

• Liferay IDE AlloyUI : Development tooling for the AlloyUI framework.

• Liferay IDE XML Search: The XPath-based search tab in the Search menu.

Why is this happening?
The dependencies for these features were hosted in an external repository that we no longer have access to. This is blocking us from building and releasing new versions of LDS. Removing these features is the only path forward to unblock the release of new LDS versions and ensure we can continue delivering updates to our users.

What this means for our users?
While these features provided value in certain contexts, they haven't been maintained in some time and may no longer provide a quality experience for our customers.
Several alternatives are available in order to ensure existing workflows aren't interrupted:

• Liferay Upgrade Planner

  • The Deprecations and Breaking Changes Reference page is our source of truth for breaking changes with each Liferay release.

  • The upgradeSourceCode command in Blade is actively maintained and offers robust code upgrade automation to handle migrations to newer Liferay versions.

• Liferay IDE AlloyUI

  • For AlloyUI development, the built-in features provided by the Web Tools Platform should provide similar functionality OOTB, though additional configurations may be needed to enable autocomplete and syntax highlighting for AlloyUI. Third-party plugins such as Eclipse Wild Web Developer are also available on the Eclipse Marketplace which offer robust JavaScript support.

    • The taglib metadata can be found here.

• Liferay IDE XML Search

  • If users need XPath-based searching functionality for XML files, Eclipse Marketplace has additional plugins available such as Eclipse XPath Evaluation Plugin.

Note: Developers still requiring these features can remain on their current version of LDS until they have completed their code migration or AlloyUI related tasks.

As it was communicated in 2025, Elasticsearch 7 has reached end-of-life on Jan 15, 2026 and is no longer available as a supported search engine for Liferay DXP.

2026.Q1 ships with a native Elasticsearch 8 connector as the default, bundled integration allowing to operate Liferay with Elasticsearch 8.19.

What changed?

The Edit and Edit in P1 actions in the Publications review screen now redirect users to the appropriate editing experience, depending on the page type:

• Content Pages → Page Builder interface

• Widget / Portlet Pages → Page editing interface (builder-like experience)

• Page Templates → Template editor

• Non-content pages (Panel, Page Set, URL, Embedded, Link to Page) → Configuration screen

Previously, users were often redirected to configuration screens even when they needed to edit layout or content.

Why was this change made?

Reviewers frequently need to make small fixes while reviewing changes. Sending users to the wrong screen slowed down reviews and increased frustration.

This update aligns the edit action with user intent, allowing faster corrections and keeping users inside the Publications workflow.

How should I update my features or implementation?

No changes are required.