Adobe Experience Manager (AEM) is now available as a Cloud Service, the cloud-native way of leveraging the AEM applications. For existing users, the transition journey to AEM as a Cloud Service involves three phases — Planning, Execution, and Post Go-live.
We at Adobe, are constantly trying to make the transition journey faster and easier for users. One such initiative is developing code refactoring tools to make existing content (code, package structure, indexes, configurations) compatible to AEM as a Cloud Service.
This article outlines the Repository Modernizer tool which changes existing AEM Maven projects to be AEM as a Cloud Service compatible by ensuring that they respect the split of mutable and immutable content, dependencies are established to create non-conflicting, deterministic deployments and that they are packaged in a deployable structure.