The AEM Utils is a developer toolkit engineered to modernize and streamline the development experience on Adobe Experience Manager.
The library is designed to provide type-safe, functional handling for legacy AEM APIs, transforming traditional JCR and Sling interactions into a more predictable and robust developer experience.
This toolkit provides a foundational set of services and utilities essential for almost all AEM projects. Whether you are building complex search components, handling hierarchical content inheritance, or managing resource lifecycles, these utilities offer the reliable core functionality required for modern AEM implementations.
| Feature | Description |
|---|---|
| annotations |
|
| constants |
|
| exceptions |
|
| java |
|
| jcr |
|
| link |
|
| query |
|
| sling |
|
| wcm |
|
| Feature | Description |
|---|---|
| cronjobs |
|
| httpclient |
|
| inmemorycache |
|
| runmode |
|
Add the aem-utils.all and aem-utils.core-bundle artifact to the <dependencies> section
<dependency>
<groupId>com.merkle.oss.aem</groupId>
<artifactId>aem-utils.all</artifactId>
<version>5.1.2</version>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.merkle.oss.aem</groupId>
<artifactId>aem-utils.core-bundle</artifactId>
<version>5.1.2</version>
<scope>provided</scope>
</dependency>
Embed the package into your core module to make use of the Java API:
<dependency>
<groupId>com.merkle.oss.aem</groupId>
<artifactId>aem-utils.core-bundle</artifactId>
</dependency>
Embed the package into your all deployment module using the filevault-package-maven-plugin:
<embedded>
<groupId>com.merkle.oss.aem</groupId>
<artifactId>aem-utils.all</artifactId>
<target>/apps/{your/install/path}/install</target>
</embedded>
Build the full package
mvn clean install -PautoInstallBundle
Build and deploy the full package to a local AEM Author:
mvn clean install -PautoInstallPackage
This tool requires AEM Version 2026.6.26635.20260611T122956Z-260500 or higher.
- AEM as a Cloud Service (AEMaaCS): This tool is primarily designed and optimized for AEMaaCS environments.
- AEM On-Premise / Adobe Managed Services (AMS): While the codebase is compatible with standard AEM On-Premise/AMS installations, please note that it has not been formally tested in these environments.