Hi @LearningisKey I found only this old thread on something similar, nothing else out there. Please check if it helps. It talks about permissions on AEM server's folder location on the OS:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-3-package-installation-issue/td-...

AEM Taxonomy is more like a concept, a best practice on how to organize things as per your needs. A taxonomy can vary a lot depending on what each project needs to implement. But at the end of the day it a custom scheme meant to ease your work by categorizing things into groups or classes or however...

Hi @Sb2512 There is no replacement yet for this, so you may still need to use the existing org.apache.commons.lang.text.StrLookup class. Neither AEM 6.5 not the cloud service version don't have this updated yet:- https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javado...

I used to have only one repository as well and the structure I suggested worked fine with that. So, the reactor pom.xml file would look something like this: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-...

Hi @anjabed Could you post here some snapshot of the dialog definition and of the custom validation JS (supposing you added one) ? It would be easier get some advice once your specific scenario becomes more clear.

Hi.I will not get into the pros and cons of actually having this. But if you really want it, I guess you could have one dedicated Maven module for each site. Something like: site-a core ui.apps ui.content ui.frontent ... site-b core ui.apps ui.content ui.frontent ... commons core ui.app...

Can you try commit outside Eclipse, in command line or smth ?

Hi @KNan  Take a look in here: https://experienceleague.adobe.com/en/docs/experience-manager-learn/ams/dispatcher/git-symlinksMaybe you can set symlinks = true in your gitconfig file.

Hi @dylanmccurry  The only options I am aware of are:1. Manually delete the target folder from your project2. Restart the IDE, in your case VSCode3. Run Maven one time with -Dmaven.clean.failOnError=false parameter

Hi @Veena1  Ideally would be to have simply the page structure, of course without affecting the UX/UI. Not sure how hard would such a rework be for your team. If that is out of question, you could try indeed to create XFs. I imagine the page itself would become lighter, even if the total amount of c...