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

Use compile scope to transitively inherit acs-aem-commons-bundle #3317

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

kwin
Copy link
Contributor

@kwin kwin commented Apr 9, 2024

This eases introducing Cloud-only API as the consumer should only depend on "acs-aem-commons-bundle-cloud" instead of "acs-aem-commons-bundle" (when running in AEMaaCS)

@kwin kwin requested a review from davidjgonzalez April 9, 2024 18:28
This eases introducing Cloud-only API as the consumer should only depend
on "acs-aem-commons-bundle-cloud" instead of "acs-aem-commons-bundle"
(when running in AEMaaCS)
@kwin kwin force-pushed the bugfix/scope-of-bundle-in-bundle-cloud branch from 08e55c4 to 919cc68 Compare April 9, 2024 18:29
@kwin kwin marked this pull request as draft April 10, 2024 10:59
@kwin
Copy link
Contributor Author

kwin commented Apr 10, 2024

It is hard to exclude a dependency including its transitive dependencies in https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html. Also I stumbled upon https://issues.apache.org/jira/browse/MENFORCER-502 which leads to different behaviour when building the module standalone (success) vs in the multimodule build (failure)

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

Successfully merging this pull request may close these issues.

2 participants