AEM Project Repository Structure Package details | Community
Skip to main content
Level 2
January 29, 2022
Solved

AEM Project Repository Structure Package details

  • January 29, 2022
  • 3 replies
  • 1061 views

I  created a project for AEM cloud .

 

In project structure ,i found ui.apps and ui.apps.structure and ui.config.

 

in ui.apps(pom.xml) and ui.config(pom.xml) has following entries as common.

 

    <repositoryStructurePackages>

                        <repositoryStructurePackage>

                            <groupId>sample</groupId>

                            <artifactId>sample.ui.apps.structure</artifactId>

                        </repositoryStructurePackage>

                    </repositoryStructurePackages>

 

ui.config

 <packageType>container</packageType> -

 

ui.apps

 <packageType>application</packageType>

 

As per documentation https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en

 

Code Packages require configuring the FileVault Maven plug-in’s configuration to reference a <repositoryStructurePackage> that enforces correctness of structural dependencies (to ensure one code package doesn’t install over another). 

 

This is only required for Code packages, meaning any Package marked with <packageType>application</packageType>.

 

As per documentation only <packageType>application</packageType> i.e ui.apps. needs to reference to repositoryStructurePackages ,y ui.config also needs.Is there any reason?

 

 

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Anish-Sinha

Hi @dillibabu77 ,
You are correct. <repositoryStructurePackage> needs to be included for the code deployment. And if you notice, eventually ui.config is part of code. It does contains the configuration files but this is done for the proper segregation purpose. It does modify the nodes in /apps structure. So, you consider anything that goes to /apps as code package. Let me know if this makes sense.

3 replies

JeevanRaj
Community Advisor
Community Advisor
January 29, 2022

Hi @dillibabu77 

 

 

The below article sheds more light into repository structure package specifically in AEM as a cloud.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/repository-structure-package.html

 

Thanks

Anish-Sinha
Adobe Employee
Anish-SinhaAdobe EmployeeAccepted solution
Adobe Employee
January 29, 2022

Hi @dillibabu77 ,
You are correct. <repositoryStructurePackage> needs to be included for the code deployment. And if you notice, eventually ui.config is part of code. It does contains the configuration files but this is done for the proper segregation purpose. It does modify the nodes in /apps structure. So, you consider anything that goes to /apps as code package. Let me know if this makes sense.

Himanshu_Singhal
Community Advisor
Community Advisor
January 30, 2022

@dillibabu77  As described by @anish-sinha, ui.config is also falls under /apps hence it also under repositoryStructurePackages.