Expand my Community achievements bar.

SOLVED

Not able to see <project>-packages in crx in dev environment in AEM as cloud service

Avatar

Level 2

Hi,
Just wanted to ask <project>-packages is hidden in crx in cloud service? but my backend is working but not able to see application/install
for ex test-pro is there but not test-pro-packages folder.

skchauhan_0-1716476923052.png

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

When you build your project locally, your deployment package embeds the JAR files in content packages (typically /apps/<project>/install), and AEM 6.5 and the SDK pick them up from the repository (using the JcrInstaller).

 

In AEM CS this is not done anymore. There the build process extracts these binaries from the content package and ships it the same way as AEM product bundles; they are no longer part of the repository. This is the behaviour you observe.

 

View solution in original post

2 Replies

Avatar

Community Advisor

@skchauhan 

 

AEM as a Cloud Service, the traditional CRX Package Manager (/crx/packmgr) is not directly accessible for security reasons. The /etc/packages folder where packages are typically stored is also hidden by default.
 
To manage packages (upload, install, build, delete) in AEM Cloud Service, you need to use a custom tool or service like the Package Handler instead of the traditional CRX Package Manager.

You can check this documentation about package manager in AEMaaCS
 

Avatar

Correct answer by
Employee Advisor

When you build your project locally, your deployment package embeds the JAR files in content packages (typically /apps/<project>/install), and AEM 6.5 and the SDK pick them up from the repository (using the JcrInstaller).

 

In AEM CS this is not done anymore. There the build process extracts these binaries from the content package and ships it the same way as AEM product bundles; they are no longer part of the repository. This is the behaviour you observe.