AEM Cloud multi module project | Community
Skip to main content
N
nj2
Level 3
March 2, 2023
Solved

AEM Cloud multi module project

  • March 2, 2023
  • 1 reply
  • 1966 views

Hi All, 

What would be the recommended approach for adding a new module for AEM Guides in existing AEMaaCS project structure based on Archtype 23. 

shoule we create a module or create a separate project or any other approch. Can someone please share pros and cons of both the approaches?

 

TIA

 

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 Jagadeesh_Prakash

@nj2 No need to create a complete new one. Generate a new project and comment out the unnecessary modules

 

for ex: as in the multi tenant structure i suggested dispatcher will be a individual tenant, so you can comment out the dispatcher module in the new generated code and then move the dispatcher code to the individual dispatcher tenant. 

 

In the similar case for UI frontend. We have done this solution for multiple clients and currently working on the same.

 

In cloud manager you can not have 2 repository projects deployed to same environment with different piplelines. It will overwrite the existing project. You can DM me I can explain you in a better way. 

1 reply

Jagadeesh_Prakash
Community Advisor
Jagadeesh_PrakashCommunity Advisor
Community Advisor
March 2, 2023

Hi @nj2 

 

In AEMaaCS If you need to create a mult-tenant or multi module projects. Make sure you generate the default project from the cloud manager repository and use below script to generate the individual tenants modules.

mvn -B archetype:generate `
  -D archetypeGroupId=com.adobe.granite.archetypes `
  -D archetypeArtifactId=aem-project-archetype `
  -D archetypeVersion=23 `
  -D aemVersion=6.5.0 `
  -D appTitle="First App Example" `
  -D appId="first-app" `
  -D groupId="co.dlighthouse.aem.firstapp" `
  -D frontendModule=none `
  -D includeExamples=y `
  -D includeDispatcherConfig=n

https://www.dlighthouse.co/2020/06/creating-aem-application-using-adobe-archetype-23.html

 

Below are observations:

1. Make sure that dispatcher is a individual tenant on top of all tenants. Remove the dispatcher in individual tenants

2. In the main parent pom.xml make sure you add the individual modules to build

 

 

    N
    nj2Author
    Level 3
    March 2, 2023

    thank you @jagadeesh_prakash , If I want to add a new module to my existing project, do I need to create a completely new one. That approach does not seem appropriate to me. It was created three years ago, and now I'd like to add one new module to it.

      Jagadeesh_Prakash
      Community Advisor
      Jagadeesh_PrakashCommunity AdvisorAccepted solution
      Community Advisor
      March 3, 2023

      @nj2 No need to create a complete new one. Generate a new project and comment out the unnecessary modules

       

      for ex: as in the multi tenant structure i suggested dispatcher will be a individual tenant, so you can comment out the dispatcher module in the new generated code and then move the dispatcher code to the individual dispatcher tenant. 

       

      In the similar case for UI frontend. We have done this solution for multiple clients and currently working on the same.

       

      In cloud manager you can not have 2 repository projects deployed to same environment with different piplelines. It will overwrite the existing project. You can DM me I can explain you in a better way. 

        Terms & ConditionsAccessibility statement

        Loading footer...