Cloud Manager deprecations warnings for acs-aem-commons-all cloud

[robrat]

Adobe deprecated some packages and wants to remove them in the future. The deprecation warnings are also emitted for com.adobe.acs:acs-aem-commons-all_6.15.0-cloud:

2026-02-06 15:49:39.332 [region-deprecated-api] com.adobe.acs:acs-aem-commons-bundle:6.15.0: Usage of deprecated package found : org.apache.sling.commons.json : Usage of this deprecated API is not supported in AEM as a Cloud Service. Deprecated since 2022-12-31 For removal : 2023-02-28

2026-02-06 15:49:39.332 [region-deprecated-api] com.adobe.acs:acs-aem-commons-bundle:6.15.0: Usage of deprecated package found : com.github.jknack.handlebars : com.github.jknack.handlebars package is deprecated and marked for removal in subsequent releases which will involve removal of the handlebars dependency in AEM. Deprecated since 2024-07-10 For removal : 2025-01-10

The Adobe documentation does not mention a date yet, but those warnings should nevertheless be fixed.

[alexanderigeorgiev]

Hello,
Yesterday Adobe send an email stating that after:
"March 30
Pipelines containing code that uses deprecated APIs will fail during the Code Quality step. Deployments will be blocked until the deprecated API usage is removed. This may prevent you from releasing time-sensitive updates and could impact your business operations."

So can you increase priority of this issue.
We are using the latest acs commons 6.16 and still have the warning about deprecated package found: org.apache.sling.commons.json

There is another warning, that I guess is with lesser priority, since it is not supposed to block deployment:
[bundle-unversioned-packages] com.adobe.acs:acs-aem-commons-bundle:6.16.0: Bundle acs-aem-commons-bundle:6.16.0 is importing packages [com.amazonaws.services.s3, com.amazonaws.auth, com.github.benmanes.caffeine.cache.stats, twitter4j.json, twitter4j.auth, twitter4j.conf, twitter4j, com.amazonaws.services.s3.model, com.github.benmanes.caffeine.cache] without specifying a version range.

[stefanseifert]

regarding the deprecating warning for org.apache.sling.commons.json - that API is deeply tied into the AEM product API. if you use certain parts of the AEM API, you have no other chance than having a dependency to org.apache.sling.commons.json as well.

for ACS AEM Commons, this is for example this class https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/wcm/impl/WorkflowModelFilterPageInfoProvider.java which implements this interface https://developer.adobe.com/experience-manager/reference-materials/6-5/javadoc/com/day/cq/wcm/api/PageInfoProvider.html (same for AEMaaCS API https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/day/cq/wcm/api/PageInfoProvider.html) - and this interface has a direct dependency to org.apache.sling.commons.json.

there are other examples e.g. https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/day/cq/wcm/api/components/DropTarget.html which is used by https://wcm.io/handler/commons/ which leads to the same problem.

so Adobe should either disable the warning about org.apache.sling.commons.json in cloud manager, or find a way to eliminate this dependency from their own API (which is likely impossible without breaking the API). in any case, it must not ever turn out to be a blocker for a cloud manager deployment if this dependency is used.

of course, you should stay away from org.apache.sling.commons.json wherever possible in your own code, but in some cases it's just not possible when those parts of the AEM API are involved.

(having said that, in ACS AEM Commons there are other places where org.apache.sling.commons.json is still used without need, and those usages should be replaced)

[kwin]

Look at #3256 for a discussion related to o.a.sling.commons.json.
Regarding Handlebars I opened #3712.