Repository structure package

Hi everyone. My name is Abhishek Dwevedi and in this video we are going to learn about Repository Structure Package.

After completing this video you should be able to describe Repository Structure Package and you should also be able to explain need and usage of Repository Structure Package. The Repository Structure Package defines the expected, common state of/apps folder which the package validator uses to determine areas safe from potential conflicts as they are standard roots. Even projects for Adobe Experience Manager as a cloud service requires a Repository Structure Sub Package definition. Its sole purpose is to define the GCR repository routes in Vista projects, code sub packages deployed.

This ensures the installation of packages in Experience Manager as a cloud service is automatically ordered by GCR resource dependencies. Missing dependencies may lead to scenarios where substructures would be installed ahead of the appearance structures and therefore be unexpectedly removed, breaking the deployment. If your code package deploys into a location which is not covered by code package, then any ancestor resources must be enumerated in Repository Structure Package to establish these dependencies. The Repository Structure Sub Package does not have any content of its own. It is only comprised of a pom.xml file which defines the filter rules.

Now let’s see the Repository Structure Package and inspect some important elements of it.

So, as we have already created this project using Maven archetype, hence this Repository Structure is already created for us. Now let’s go into this Repository Structure and open this pom file.

Well, the most important part of this pom file is these filters. So here you can see the important filters which are required, which we have declared here for the usage in our project. The next thing that we need to do is we need to add this Repository Structure Module in our UI apps pom file because this affects /apps directly. So, let’s go to UI apps folder and open that pom file.

And in this pom file we should be having a Repository Structure Packages node which contains all the details about this module. If you’re done with these two things then you are good to use Repository Structure Packages.

Now you should be able to describe Repository Structure Package and should also be able to explain need and usage of Repository Structure Package. Thank you for watching this video. Have a great day. -