Removed 26 February 2026
AEM Cloud Service APIs removed on 26 February 2026
Adobe set a removal date of 26 February 2026 for a group of long-deprecated packages. Cloud Manager first paused pipelines at the Code Quality step when code used them, then from 14 April 2026 failed those pipelines outright, and from 28 September 2026 environments still using them stop receiving critical Adobe release updates.
Affected packages and APIs
org.apache.log4jch.qos.logback.classicorg.eclipse.jetty.*org.apache.sling.commons.authorg.apache.felix.http.whiteboardcom.mongodborg.apache.abderaorg.apache.cocoon.xmlorg.slf4j.spi / org.slf4j.eventcom.drew.*org.apache.felix.webconsolecom.google.common.*
What to use instead
SLF4J for logging, Sling Auth Core for authentication, the OSGi Http Whiteboard for servlets and filters, and your own embedded library versions for Jetty client, Guava or metadata extraction.
How to fix it
- Compile against the current aem-sdk-api; removed packages fail to resolve, which gives you an exact list.
- Replace org.apache.log4j and Logback calls with org.slf4j.Logger.
- Move org.apache.sling.commons.auth(.spi) usage to org.apache.sling.auth(.spi).
- Where a third-party library is truly needed, embed a current version in your bundle rather than relying on the platform export.
- Run the Cloud Manager pipeline; the Code Quality step must pass without overrides.
AEM 6.5
import org.apache.log4j.Logger;
public class PriceService {
private static final Logger LOG = Logger.getLogger(PriceService.class);
}Cloud Service
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public class PriceService {
private static final Logger LOG = LoggerFactory.getLogger(PriceService.class);
}How we detect it
- Readiness scan rule
removed-apis-2026: APIs removed from Cloud Service in February 2026.
Best Practices Analyzer reports it under OCU, OU.
Can agents fix it?
High. Import swaps and logger rewrites are mechanical; agents produce them as reviewed pull requests.
Source: Adobe Experience League. Checked 19 October 2026.