ACS Commons is not appearing in tools.

[AmitaJ]

Hi Everyone,

I am trying to install ACS Commons in AEM as a Cloud Service and have followed the official documentation:
https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html

In my all pom.xml, I have added the following configuration:

<embedded>
    <artifactId>acs-aem-commons-all</artifactId>
    <target>/apps/xyz-vendor-packages/container/install</target>
    <filter>true</filter>
    <isAllVersionsFilter>true</isAllVersionsFilter>
</embedded>

<dependency>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-all</artifactId>
<classifier>cloud</classifier>
<version>6.9.2</version>
<type>zip</type>
</dependency>

In my pom.xml added below code -

<dependency>
  <groupId>com.adobe.acs</groupId>
  <artifactId>acs-aem-commons-bundle</artifactId>
  <version>6.9.2</version>
  <scope>provided</scope>
</dependency>

Everything works perfectly in the local AEM SDK, but when I deploy to AEM as a Cloud Service, ACS Commons does not appear under Tools.

I have validated that /apps/acs-commons exists on the Cloud Author instance. However, it is missing from /apps/cq/core/content/nav/tools.
I also have a custom utility (xyz-utility) already present under this path, but it is not overriding or merging with ACS Commons in the Tools navigation.

Could someone please help clarify why this is happening, and how to make ACS Commons appear under the Tools menu in AEM as a Cloud Service?

Thank you.

[Mohit_Singh_01 · Accepted solution]

Hi @AmitaJ, Have you checked the compatibility version of ACS AEM Commons with your version of AEM. Is it compatible with your aem cloud version?

Please refer to check compatibility: https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html

Best Regards,
Mohit Singh

[kautuk_sahni]

@AmitaJ Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!