Cloud Manager pipeline pauses on deprecated libraries in AEMaaCS
In Adobe Experience Manager as a Cloud Service, Cloud Manager pipelines stop or fail when deprecated library usage is detected during code scanning or analysis. These alerts appear in Actions Center and block deployments when deprecated packages remain in customer code or dependencies. To fix this issue, identify the flagged package, remove or replace it, and validate through a fresh pipeline execution.
Description description
Environment
Adobe Experience Manager as a Cloud Service
Issue/Symptoms
- Cloud Manager pipeline pauses or fails in the Code Quality or scanning stage
- Deprecated Library Usage Detected appears in Actions Center
- Build logs show Usage of deprecated package found
- Alerts persist after dependency removal
- Unable to identify the source of the flagged package
How to confirm
- Review the alert entries and note each flagged library name.
- Search the repository and dependency tree for the library across all modules and parent POMs.
- Run
mvn dependency:tree | grep <library-name>and confirm that the package is not present. - After code changes, review the build and code quality logs for any remaining deprecated package messages.
Resolution resolution
To fix this issue, follow these steps:
-
Log in to Adobe Experience Cloud.
-
Go to AEM
>Actions Center>Program>Environment and review each incident entry to capture library names. -
Search your Git repository for the deprecated library by running:
code language-none mvn dependency:tree | grep <library-name> -
Update or replace the library using Adobe guidance from the AEM deprecated APIs list.
Replace
com.google.commonwithcom.google.guava:guava:33.4.8-jreor a higher version.If
ch.qos.logbackcomes from ACS Commons, update the ACS Commons version. -
Commit code changes and run a new Cloud Manager pipeline.
-
Return to Actions Center after the pipeline completes. Verify that no new incidents appear and the flags are resolved.