Backward Compatibility in AEM 6.5
For a list of content and configuration changes that are not under the scope the Compatibility Package, see Repository Restructuring in AEM .
In AEM 6.5, all features have been developed with backwards compatibility in mind.
In most cases, customers running AEM 6.3 should not have to change the code or customizations when doing the upgrade. For AEM 6.1 and 6.2 customers there is no additional breaking changes than would be faced during an upgrade to 6.3.
For exceptions where features could not be kept backward compatible, backward incompatibility issues for bundles and content can be mitigated by installing a Compatibility Package for 6.4 (please see how to setup below for details on where to download). This compat package will help restore compatibility in most cases for applications compliant with AEM 6.4.
The Compatibility Package allows you to run AEM in compatibility mode and defer custom development against new AEM features:
Please note that the compatibility package is only a temporary solution to defer development required for being AEM 6.5 compatible, its recommended only as a last option if you are not able to address compatibility issues through development immediately after the upgrade. It is strongly recommended to switch to native mode and uninstall the compatibility package once you decide to proceed with 6.5 based custom development and avail of full 6.5 functionality.
The Compatibility Package has two modes: Routing Enabled and Routing Disabled .
This allows AEM 6.5 to be run in three modes:
Native mode is for customers who want to use all the new features of AEM 6.5 and are ready to do some development to make their customizations work with all new features.
This means that you may need to make adjustments in your application immediately after upgrade.
Compatibility Mode: Compatibility Package Installed with Routing Enabled
Compatibility Mode is for customers who have customizations of interfaces that are not backward compatible. This allows AEM to run in compatibility mode and defer custom development required against new AEM Features that are not compatible with some of your custom code.
Legacy Mode: Compatiblity Package Installed with Routing Disabled
Legacy mode is for customers having custom interfaces based on legacy or deprecated code from AEM that has been moved out in the compatibility package.
How to Set Up
The AEM 6.3 Compatibility Package will be installable as a package using the Package Manager at this link .
Once the Compatibility Package is installed, the routing can be enabled or disabled using a switch in the OSGI configuration as shown below:
Once the Compatibility Package is installed and set up, the features will be used based on the compatibility mode that has been chosen.