Running two projects with a master project | Community
Skip to main content
New Participant
October 17, 2023
Solved

Running two projects with a master project

  • October 17, 2023
  • 1 reply
  • 705 views

Hi All,

 

We are in middle of migrating from the old code base to new codebase. As part of which I want to keep both the project running and getting deployed to AEM as Cloud Service. For this I have created this sample project structure.

 

 

My Parent pom which you see in the above screenshot below

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.ansys.aem</groupId> <artifactId>aem-master</artifactId> <packaging>pom</packaging> <version>1.0.0-SNAPSHOT</version> <name>AEM Master Platform</name> <description>AEM Master Platform</description> <modules> <module>platform</module> <module>legacy-code</module> </modules> <profiles> <profile> <id>autoInstallPackage</id> </profile> <profile> <id>autoInstallSinglePackage</id> </profile> </profiles> </project>

Consider Platform and legacy code as standard AEM projects which you would build using a normal AEM archtype. This work locally perfectly fine and deploys both the project but on cloud it fails during the build step, in the logs of build image there is nothing useful which makes sense to me. Does anybody have an idea how to solve this. I would like to keep my projects separate,  I understand that combining them into one AEM project would be a solution but we dont prefer that option.

 

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 iamnjain

Hi @shehjadk07 

 

It can be done and one suggestion, just move out the dispatcher module in parent folder, so dispatcher code can be managed and deployed from single module.

Below mentioned article can help you,

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/cloud-manager/devops/merge-projects.html?lang=en

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-cloud-manager-use-single-pipeline-to-deploy-multiple-aem/td-p/411335

 

Hope it helps.

1 reply

iamnjain
iamnjainAccepted solution
New Participant
October 17, 2023

Hi @shehjadk07 

 

It can be done and one suggestion, just move out the dispatcher module in parent folder, so dispatcher code can be managed and deployed from single module.

Below mentioned article can help you,

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/cloud-manager/devops/merge-projects.html?lang=en

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-cloud-manager-use-single-pipeline-to-deploy-multiple-aem/td-p/411335

 

Hope it helps.

New Participant
October 17, 2023

Thank you for this response so I guess I started in correct direction. I will try to move the dispatcher module out and check today hopefully it will work