Exporting an AEM Site

aradhyakasat

11-08-2020

So I have an AEM website with the entire folder structure including the core package with java files. The way I'm currently exporting it to be able to run on any other machine is that I download the "samplewebsite.all.SNAPSHOT " through CRXDE and upload the same on the other machine through CRXDE. For the core package, I do a maven build and then upload the "samplewebsite.core.SNAPSHOT" jar through system/console/bundles. I'm curious to know if this process can be reduced down to just one package upload which contains the core package files as well? 

@BrianKasingli 

Accepted Solutions (1)

Accepted Solutions (1)

BrianKasingli

MVP

11-08-2020

@aradhyakasat 

When you have an AEM content package, with a bundle (JAR FILE) within the /apps/my-site/install folder, the when the AEM content package is installed into AEM, the bundle will be atomically installed by the OSGI installer, documentation: https://sling.apache.org/documentation/bundles/jcr-installer-provider.html; taking a look at the ui.apps (AEM content package) artefact produced by the aem-project-archetype, you can see the core bundle is embedded in the /apps/my-site/install folder. 

Reducing down to one package for release is simple, you can follow how the AEM-project-archetype implements the "all" maven module, https://github.com/adobe/aem-project-archetype/tree/master/src/main/archetype/all 

 

Answers (3)

Answers (3)

RMGJID

12-08-2020

if you are working with the latest archetype, it should happen with "all" package automatically. If you still have issues, see if you have mistakenly install a versioned package/jar file that is causing problems.

Arun_Patidar

MVP

11-08-2020

Please check apps package, ui.apps package include the jar file inside /apps/proj/install. If jar is present then check filter.xml

You don't need to install jar separately. if your apps package is getting installed.

berliant

Employee

11-08-2020

As per the maven archetype 23, the "all" package includes both content and core packages. For your use-case, it should be enough to deploy only "samplewebsite.all.SNAPSHOT" package.