Solved! Go to Solution.
The ACS AEM commons should be pushed via code base.
Example: By adding following via "filevault-package-maven-plugin" in all module.
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.apps</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.content</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
You can configure "ACS AEM commons' AEM Environment Indicator"
Once configured, each environment can have a different color bar for easy visual identification.
Is ACS AEM Environment Indicator works in AEMaaCS? my understanding is that ACS AEM Commons is not compatible in AEMaaCS
Views
Replies
Total Likes
You are right. Not all features work on Cloud. In some cases, its explicitly mentioned if it works/does not work on AaaCS.
Environment Indicator should.
Let me install ACS AEM Commons in AEMaaCS and verify this. Thanks
Views
Replies
Total Likes
AEM Cloud is not allowing me to upload acs-aem-commons-content-5.4.0 package. I get below error while uploading the zip file. Error - "Package (or it's subpackage(s)) contains application content which isn't supported at runtime."
Looks like it is ACS Common is not compatible to AEM Cloud
Views
Replies
Total Likes
The ACS AEM commons should be pushed via code base.
Example: By adding following via "filevault-package-maven-plugin" in all module.
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.apps</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.content</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
Thanks for your response. We also need to add below dependency in oder to embed ACS Common