Code Repository Modernizer

Transcript

Repository Modernizer is a utility developed to restructure existing Maven project packages by separating content and code into discrete packages to be compatible with the project structure defined for Adobe Experience Manager as a cloud service. AEM requires separation of mutable and immutable content, which means a single content package cannot deploy to both apps and runtime writeable areas, e.g., slash content, slash conf, slash home of the repository. Instead, the application must separate code and content into discrete packages for deployment into AEM. The objective of this tool is to modernize any given projects into AEM cloud service compatible structure. The UI.apps package or code package contains all the code to be deployed and only deployed to apps. The UI.config package or OSGI config package contains all OSGI configurations. The UI.content package or content package contains all content and configuration. The all package container package that embeds the core bundle in UI.apps, UI.conf, and UI.content packages. After the successful conversion, the tool generates a summary report. Depending on that, take necessary steps to address manually. For example, if there are any conflicts during conversion to new package or renaming slash merging folders will be reported. Missing version info in core bundle will be reported. The version need to be added in the dependency section of the palm.xml manually. Third-party dependency bundles will be reported. Their jar files need to be placed in the non-Adobe dependency directory, which will serve as local repository. There are some known limitations which need to be addressed by the project teams. For example, it does not make any modifications to existing core bundles apart from replacing uber.jar dependencies. As an implementation, have to update required dependencies. These tools are constantly updated and new versions are released. So for more details, please refer to the documentation to get latest updates.