Resolving skipped or uninstalled packages in ÃÛ¶¹ÊÓÆµ Cloud Manager deployments
This article addresses an issue where certain content or configuration packages are skipped or not installed during ÃÛ¶¹ÊÓÆµ Cloud Manager deployments for AEM (v6.5 or AEM as a Cloud Service). The issue is often accompanied by the following errors:
- Build logs: skipped-content-package
- Package Manager: A different version seems to be installed
This affects both Author and Publish instances. To resolve the issue, adjust pom.xml
file configurations.
Description description
Environment
- Product: ÃÛ¶¹ÊÓÆµ Experience Manager (AEM)
- Versions: AEM 6.5, AEM as a Cloud Service (AEMaaCS)
- Deployment Tool: ÃÛ¶¹ÊÓÆµ Cloud Manager pipeline
Issue / Symptoms
- Packages are skipped or uninstalled during Cloud Manager deployments.
- Build logs show skipped-content-package messages.
- Package Manager displays the error: A different version seems to be installed.
- Manual installation does not persist after redeployment.
Resolution resolution
To resolve the issue, follow these steps:
- Check Cloud Manager build logs for skipped-content-package messages.
- Open the
pom.xml
files of the affected packages. - Ensure the
<cloudManagerTarget>
property is set to none. - If you find
<cloudManagerTarget>none</cloudManagerTarget>
in thepom.xml
files, remove it. - Re-run the Cloud Manager pipeline after making these changes.
3d58f420-19b5-47a0-a122-5c9dab55ec7f