We are facing issue with excludedDependencies - property, as it's not excluding classes from dependency project.
@1 will have components common for all sites, where @2 and @3 will have it's site specific components.
site1 core pom.xml have added with dependency of xyz-common-core to utilize it's service classes
Problem:
cq-component-maven-plugin generates and injects component dialogs for all identified classes in common project folder, as site1 have dependency of common again it's generates and injects component dialogs for classes exposed from common below site1 folder, so it's duplicating components.
we have added excludedDependencies property in configuration in site1 ui pom.xml.
But still the component dialogs are generated as a duplicate in site1.
We are facing issue with excludedDependencies - property, as it's not excluding classes from dependency project.
Problem: cq-component-maven-plugin generates and injects component dialogs for all identified classes in common project folder, as site1 have dependency of common again it's generates and injects component dialogs for classes exposed from common below site1 folder, so it's duplicating components. we have added excludedDependencies property in configuration in site1 ui pom.xml. But still the component dialogs are generated as a duplicate in site1.
Help us to get this issue resolved.
Project Structure: @1) xyz-common[xyz-common-core, xyz-common-ui] @2) xyz-site1[xyz-site1-core, xyz-site1-ui] @3) xyz-site2[xyz-site2-core, xyz-site2-ui]
\<excludedDependencies> \<dependency> \<groupId>com.xyz.common\</groupId> \<artifactId>xyz-common-core\</artifactId> \</dependency> \</excludedDependencies>