DocumentationExperience Cloud KCS

Remediate deprecated Google Guava API usage and update ACS AEM Commons in AEM as a Cloud Service

Last update: September 29, 2026

This article explains how to identify and resolve deprecated Google Guava API usage and ensure your ACS AEM Commons version meets compliance requirements in AEM as a Cloud Service. Addressing these issues is necessary to avoid disruption of automatic product updates after September 2026.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Cloud Manager Code Scanning and pipeline analysis
  • Project code or deployed dependencies that use com.google.common.*

Issue/Symptoms

  • You receive an Adobe notification about deprecated API usage or an ACS AEM Commons version that requires attention.
  • Cloud Manager Code Scanning logs report usage of deprecated packages such as com.google.common.*.
  • You need to remediate the finding before the applicable Adobe removal and enforcement milestones.

Cause

The project or a deployed dependency uses deprecated AEM-provided Google Guava APIs, or the project uses an ACS AEM Commons version below the current documented minimum. Several deprecated APIs are scheduled for removal on September 14, 2026. Continued usage can affect Cloud Manager deployment enforcement and access to critical Adobe release updates.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Download and review the Code Scanning step logs from Cloud Manager pipeline executions for all environments.
  2. Search the logs for entries indicating usage of deprecated APIs, such as com.google.common.*.
  3. Identify the source of the deprecated API usage by noting the specific packages, bundles, or libraries flagged in the logs.
  4. Remove or update direct and transitive dependencies that use deprecated AEM-provided Google Guava APIs. If the usage comes from a third-party library, update or replace that library when a compatible version is available.
  5. Update ACS AEM Commons to version 6.17.2 or later and use the Cloud Service classifier where applicable.
  6. Rerun the Cloud Manager pipelines after making the changes and verify that the logs for all environments no longer report the deprecated API usage.
  7. For a more comprehensive analysis, use the AEM Maven Analyzer Plugin as recommended by Adobe to systematically detect deprecated API usage.
  8. Confirm that your development environment uses the latest codebase and reflects all dependency updates before creating the next deployment.
  9. After remediation, confirm that the Code Scanning logs for all environments no longer report deprecated API usage warnings.
recommendation-more-help
experience-cloud-kcs-help-kbarticles