ACS AEM Commons 6.0.0 Planning

ACS Commons is problematic for use on AEM as a Cloud Service as it contains code that, while may not be used/usable/enable-able on AEM as a Cloud Service, it still exists in the code base and Cloud Manager flags it as problematic. Some of this code has no migration path to being supported in AEM as a Cloud Service, without change to the product itself - which is unlikely.

In ACS Commons 6.0 it would be good to create two release variants, one that contains clean AEM as a Cloud Service code (passes Cloud Manager checks, and as much as reasonable aligns with best practices) and another that contains the "classic" features that still work on AEM 6.x.

Artifact	Classifier	AEM CS compat	AEM 6.x compat	Rename?	Artifact description
content	None	Yes	Yes	content -> all	Deployment package for AEM CS
content	classic	No	Yes	content -> all	Deployment package for AEM 6.x
bundle	None	Yes	Yes	bundle -> core	Java bundle, also used as dep for APIs
bundle	classic	No	Yes	bundle -> core	Java bundle, also used as dep for APIs

Features

This table lists features, and which artifact set they will reside in (AEM CS vs Classic vs Removed entirely)

As this is a still in planning, expect this table to be frequently updated / changed.

• Deprecated features
• RequireAEM
• Incompatibility

Feature	Area/Domain	AEM CS	Classic	Remove completely	Reason, additional comments
To be removed from CS
Bulk Workflow Manager v2	#tbd	No	Yes	No	Incompatible with CS; but included features may be valuable (Workflow Manager API)
File Fetcher Checks	#tbd	No	Yes	No	Incompatible with CS
Health Checks	#tbd	No	Yes	No	Incompatible with CS
Redirect Map Manager	Redirect	No	Yes	No	Incompatible with CS; don't confuse with Redirect Manager
Not to be removed from CS
Audit Log Search	#tbd	Yes	Yes	No	AEMaaCS version should come with a CS compatible index definition
Sitemap Generator	#tbd	No	Yes	No	Core Components in AEM CS now have a Sitemap Generator (since 2.17.6)