Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Exporting an AEM Site

aradhyakasat
Level 2
Level 2

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 

1 Accepted Solution
BrianKasingli
Correct answer by
Community Advisor
Community Advisor

@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 

 

View solution in original post

7 Replies
berliant
Employee
Employee

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.

Arun_Patidar
Community Advisor
Community Advisor

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.

aradhyakasat
Level 2
Level 2

@Arun_PatidarI navigated to ui.apps package and could see the jar present there inside apps/proj/install. The issue was that it contained an older version of the core jar for some reason. I deleted it and did a clean maven install which got the latest core jar in there. Thanks for your help. 🙂

BrianKasingli
Correct answer by
Community Advisor
Community Advisor

@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 

 

View solution in original post

aradhyakasat
Level 2
Level 2
@BrianKasingli I navigated to ui.apps package and could see the jar present there inside apps/proj/install. The issue was that it contained an older version of the core jar which was then flowing as is into the all.snapshot. I deleted it and did a clean maven install which got the latest core jar in there. Thanks for your help. 🙂
RMGJID
Level 3
Level 3

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.

aradhyakasat
Level 2
Level 2
Yes, that was the issue. The version of core jar in ui.apps was an older version which is why I couldnt see my servlets in action. Thanks for your help 🙂