@krishna_sai  I dont see any reason on why this is breaking. But wanted to understand how Project A and Project B are refering to core components and to each other

@Emmalight1  can you please elobrate

@yuvinitj If pushing it from code also not working then their is some problem with the implementation. you can roleout the permissions issues and other issues by pushing it via code.    You might need to debug from AEM environment level now then

@yuvinitj That should not be the case. But can you try pushing it from filter.xml file <filter root="/etc/acs-commons/lists/xxx/comparison_table_values" mode="merge"/>

@Mario248  above solution worked for me. But you can try below script as well   filename: org.apache.sling.jcr.repoinit.RepositoryInitializer-xxxxx-sites-acls.config   # Configuration created for ACLs for user permissions scripts=["create path /content/dam/xxxxxx/us-marketing-team(sling:Folder)/jcr:...

Here are some advantages of using AEM Forms JEE over AEM Forms OSGi Support for clustering: AEM Forms JEE provides support for deploying forms to a clustered environment, which can improve performance and scalability. With AEM Forms OSGi, clustering is not supported. Legacy application integration...

@Mario248 Below is one good example which is working for us   { "scripts": [ "create path (sling:OrderedFolder) /content/dam/xyz", "create path (nt:unstructured) /content/dam/xyz/jcr:content", "set properties on /content/dam/xyz/jcr:content", "set cq:conf{String} to /c...

@kavalidurga  Seems the package is not available as a bundles so can you try reffering to below URL    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/getting-error-while-building-maven-project-quot-bundle-aem/m-p/433445     you can try to follow the step 2 in this blog - h...

yes it should work. @kavalidurga 

@kavalidurga In 6.5 AEM i recommend below dependency    <dependency><groupId>com.adobe.aemfd</groupId><artifactId>forms-sdk</artifactId><version>6.5.0</version><scope>provided</scope></dependency>