DocumentationExperience Cloud KCS

Resolving deprecated library usage warnings for ch.qos.logback and removed APIs in Cloud Manager

Last update: June 27, 2026

Cloud Manager reports deprecated library usage for ch.qos.logback or other removed APIs during build, code quality, or deployment steps. These warnings come from outdated ACS AEM Commons versions, an incorrect Maven classifier, or customer code that directly references removed APIs. In some cases, Logback references originate from Adobe-managed platform bundles and don’t require any customer changes. Identifying the exact source — ACS Commons version, classifier mismatch, customer code, or Adobe runtime — determines the correct fix.

Description description

Issue: Cloud Manager flags deprecated ch.qos.logback or removed API usage during build or code quality checks

Description

Cloud Manager Action Center alerts or pipeline failures indicate deprecated usage of ch.qos.logback or other removed APIs. These warnings appear in the build phase under region-deprecated-api or configuration-api checks. The root cause varies: outdated ACS AEM Commons versions pull Logback transitively, the wrong Maven classifier is used, customer code references removed APIs, or Adobe-managed internal bundles register Logback at runtime without affecting the build.

Environment:

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Cloud Manager (build, code quality, and deployment pipelines)
  • ACS AEM Commons

Issue/Symptoms:

  • Cloud Manager build logs show: Usage of deprecated package found : ch.qos.logback.* : This internal logback API is not supported by AEM as a Cloud Service
  • Runtime logs contain entries such as ServiceEvent REGISTERED [ ch.qos.logback.core.filter.Filter] even when customer code doesn’t use Logback
  • Build compilation fails with errors related to deprecated APIs, such as RequestResponseFactory
  • Code Analyzer reports errors such as Service.ranking is not of type Integer or warnings from groovy-all:2.4.15
  • JSP precompiler failures appear after upgrading ACS Commons: File tld:http://sling.apache.org/taglibs/sling/1.0 not found

Root cause:

Deprecated library warnings occur when Cloud Manager detects use of APIs scheduled for removal. Older ACS AEM Commons packages include ch.qos.logback transitively, and using the on-prem ACS Commons classifier on AEMaaCS also triggers this warning. Customer code referencing APIs deprecated in Cloud Service — such as com.day.cq.contentsync.handler.util.RequestResponseFactory — produces similar failures. Logback references from Adobe-managed platform bundles won’t cause deployment blocks and don’t require customer action.

How to confirm

  1. Review Cloud Manager build logs for entries referencing ch.qos.logback.*, groovy-all:2.4.15, com.day.cq.contentsync.handler.util, or ACS Commons bundle versions. If logs aren’t accessible, download them via Cloud Manager > Pipelines > Execution > Logs.

  2. Confirm the exact ACS Commons version by locating lines such as com.adobe.acs:acs-aem-commons-bundle:5.2.0 or warnings referencing Logback.

  3. Run a full Maven dependency tree to check for conflicting versions:

    code language-none 
    mvn dependency:tree -Dincludes=com.adobe.acs:acs-aem-commons*

  4. Search customer-owned files for any direct Logback references:

    • Windows:

      code language-none 
      findstr /S /N /I "ch.qos.logback" pom.xml *.xml *.yml *.yaml

Resolution resolution

  1. ACS Commons version or classifier mismatch (most common): Check your project’s all/pom.xml for the ACS Commons dependency. Ensure <classifier>cloud</classifier> is present and the version is at least 6.11.0. The entry should resemble:

    code language-none 
    <groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-all</artifactId>
<version>6.16.0</version>
<classifier>cloud</classifier>

If conflicting versions appear in the dependency tree, remove any direct or transitive references to older ACS Commons builds.

2. Customer code referencing removed APIs: Search your codebase for deprecated packages flagged in Cloud Manager logs. Replace usages of removed APIs such as RequestResponseFactory with the Sling builder APIs (org.apache.sling.api.request.builder.Builders or SlingUriBuilder). Re-run Cloud Manager Code Scanning to confirm no deprecated API warnings remain.
3. JSP precompiler failures after an ACS Commons update: Add the Sling JSP Taglib dependency to your ui.apps module with scope=provided:

<groupId>org.apache.sling</groupId>
<artifactId>org.apache.sling.scripting.jsp.taglib</artifactId>
<version>2.4.0</version>
<scope>provided</scope>

Re-run the pipeline and confirm the tld not found error is gone.

4. aemanalyser configuration errors on later versions: If version 1.6.16 returns errors such as Service.ranking is not of type Integer, switch to version 1.6.4 or 1.6.14. Re-run the pipeline and confirm it completes without analyzer errors.
5. groovy-all:2.4.15 flagged as deprecated: Replace with the Orbinson Groovy Console variant:

<groupId>be.orbinson.aem</groupId>
<artifactId>aem-groovy-console-all</artifactId>
<version>19.0.8</version>
<type>zip</type>

Confirm Code Quality step reports no groovy-all warnings. If Groovy Console isn’t in use, remove it entirely.

6. Logback references from Adobe-managed bundles only: If Code Quality shows no deprecated library warnings and the only Logback entries are runtime-only lines such as ServiceEvent REGISTERED [ ch.qos.logback.core.filter.Filter] in logs — with no warnings in the build step — no action is required. These originate from Adobe platform bundles and don’t block deployment.
7. Validate: Start a new Code Scanning or Full Pipeline run. Confirm build logs show no ch.qos.logback entries under region-deprecated-api and no deprecated API warnings for customer code or ACS Commons.

recommendation-more-help
experience-cloud-kcs-help-kbarticles