Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

excludedDependencies is not excluding classes from dependency #77

Open
dharsans opened this issue Aug 28, 2018 · 0 comments
Open

excludedDependencies is not excluding classes from dependency #77

dharsans opened this issue Aug 28, 2018 · 0 comments

Comments

@dharsans
Copy link

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.

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>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant