Is there any guide on how to create local git repository and put default AEM multimodule project in that?

[Former Community Member]

Hi,

I have created a AEM project using AEM plugins default archetype. Now I want to create and push the code to my local Git in a new repository.

But I am facing an issue in creating local Git repository with the multi module archetype of AEM. Can anyone suggest a link to a good stepwise guide?

I somehow managed push to local repos., then I lose AEM perspective features like: I cannot see nodes/properties in JCR Properties view any more etc. And if I do Team>Share Project>Git....it looses its tree/structure. 

Any help will really appreciated.

Rohan

[Former Community Member]

I think I found a workaround last night, so here are the steps:

1. Created multi-module AEM project with default archetype in Eclipse. Say 'sample' so you have 6 folders shoing in eclipse namely - sample, sample.core, sample.it.launcher, sample.it.test, sample.ui.app, sample.ui.content

2. Copy and backup your 'sample' folder content from file system, you can copy from your workspace.

3. Start sharing the project from Team menu, Team>Share Project>Git and then select you local repository, but never do the root folder first, here 'sample, folder in project explorer in this example.

4. Keep in mind you should do the root folder(sample) in the last.

5. You end-up loosing content/folders inside the root folder(sample). So go to your repository and paste you backed-up contents to 'sample' folder in local git repository folder.

I am still looking to get a right approach, but it worked for me as workaround so thought to share. Please answer if anyone has the right steps to do the same.

Rohan.

[Former Community Member]

Hi All,

Can anybody let me know the way to get rid of this problem? Or is this not possible for Git to tackle multi module Maven project without loosing its structure/tree. As its in default AEM Archetype?

Please answer.

Rohan.

[smacdonald2008 · Accepted solution]

I do not think this is captured in a formal document. Each dev team has its own way of placing code in Github or other online storage systems like Bitbucket. Take a look at how some Adobe CQ teams place their code in Git as an example:

https://github.com/joerghoh/cq5-healthcheck

https://github.com/Adobe-Consulting-Services/acs-aem-commons/tree/release/1.7.4