AEM as a Cloud Service: persistent deprecated Java API alerts after ACS Commons upgrade
If deprecated Java API alerts persist after you upgrade ACS AEM Commons (ACS Commons), the packages are likely still referenced in your own code or in an Adobe out-of-the-box library. Run the AEM Analyzer Maven Plugin to find them, then refactor any usage in your own code.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Issue/Symptoms
After upgrading the ACS Commons library to the latest version, deprecated Java API alerts might still appear in your AEM as a Cloud Service environment. Common deprecated packages include:
com.day.cq.wcm.commons(deprecated since 2026-07-01, target removal 2027-03-31)org.apache.sling.commons.json(deprecated since 2023-05-15, target removal 2027-12-31, tentative)
A typical Analyzer warning for this looks like:
[ WARNING] [ region-deprecated-api] com.example:my-project.core:1.0.0-SNAPSHOT: Usage of deprecated package found: com.day.cq.wcm.commons — Deprecated since 2026-07-01. For removal: 2027-03-31
These alerts might persist even after updating dependencies, and there may be concerns about whether these deprecated APIs will block environment upgrades or updates. In some cases, AEM Core Components or Adobe-provided APIs might also reference these deprecated packages, which is why the alert can remain even after your own code is fully remediated.
Cause
Deprecation alerts persist because the deprecated APIs are still present in your codebase or are referenced by out-of-the-box (OOTB) AEM libraries, such as Core Components. Only deprecated APIs with a target removal date on or before February 26, 2026 currently block Cloud Manager pipeline deployments; APIs with later target removal dates are flagged for future remediation but do not currently block updates. See Deprecated and Removed Features and APIs for the complete list of deprecated packages, dates, and the full blocking timeline.
Resolution resolution
Follow the steps below to resolve the issue.
-
Use the AEM as a Cloud Service SDK Build Analyzer Maven Plugin to identify deprecated API usage in your codebase. See the Build Analyzer Maven Plugin documentation for setup and execution, and the Find and remove deprecated APIs tutorial for a walkthrough.
-
Review the deprecation warnings generated by the Analyzer plugin or Cloud Manager pipeline logs. Focus first on APIs with a target removal date on or before February 26, 2026, since these can block your pipeline’s Code Quality step.
-
For each deprecated API usage found:
- If the API is used in your own custom code, refactor it to use the recommended replacement listed in Deprecated and Removed Features and APIs.
- If the deprecated API is referenced only by Adobe OOTB libraries or AEM Core Components (not your own code), this is expected while Adobe’s own remediation work is ongoing. It does not currently block your environment updates as long as its target removal date is after February 26, 2026.
-
After remediating deprecated API usage in your code, rerun your Cloud Manager pipeline to confirm the alerts are resolved.
-
Continue to monitor for new deprecation alerts and review the current AEM as a Cloud Service release notes for updates on deprecated and removed features.