Not supported on Cloud Service

Splitting mutable and immutable content packages for AEM Cloud Service

Adobe's notable changes state that /apps and /libs are immutable at runtime. A package that installs both /apps and /content will not deploy; code and content travel in separate packages wrapped in an all container.

What to use instead

The AEM project archetype layout: ui.apps for immutable code, ui.content for mutable content, ui.config for OSGi configuration, and an all package. The Repository Modernizer restructures existing projects.

How to fix it

1. Run the Repository Modernizer (aio-cli-plugin-aem-cloud-service-migration) on the project.
2. Move anything written at runtime under /apps (for example generated configs) to /conf or /var.
3. Check filter.xml roots so no package mixes /apps with /content, /conf or /var.

How we detect it

• Readiness scan rule mixed-package: Content package mixing /apps with /content or /conf.

Best Practices Analyzer reports it under CAV, LOCP.

Can agents fix it?

Partial. The restructure is tool-driven; runtime writes to /apps need code changes.

Source: Adobe Experience League. Checked 19 October 2026.