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

Cloud Manager CICD PackageOverlap bug #272

Open
knennigtri opened this issue Aug 2, 2021 · 1 comment
Open

Cloud Manager CICD PackageOverlap bug #272

knennigtri opened this issue Aug 2, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@knennigtri
Copy link
Contributor

Expected Behaviour

The WKND code should have less than 1 number of open issues when the code is run through the Cloud Manager CICD pipeline

Actual Behaviour

When including the WKND code as a 3rd party maven embed in my all/pom.xml, the Cloud Manager CICD code quality produces 2 Major bugs for PackageOverlap with ui.content.sample and ui.content. I have this occurring on 2 separate demo projects with the same Open issues. These issues are not blockers of the pipeline, but if the filter statements can be updated to remove these issues, that would be helpful!

File Location Line Number Issue Type Severity Effort Rule Tags Documentation
com.adobe.aem.guides:aem-guides-wknd.ui.content.sample:1.0.0 0 affected path /content/wknd/jcr:content/image/file/jcr:content/dam:thumbnails overlaps [com.adobe.aem.guides:aem-guides-wknd.ui.content:1.0.0] Bug Major   PackageOverlaps aem https://www.adobe.com/go/aem_cmcq_packageoverlaps_en
com.adobe.aem.guides:aem-guides-wknd.ui.content.sample:1.0.0 0 affected path /content/wknd overlaps [com.adobe.aem.guides:aem-guides-wknd.ui.content:1.0.0] Bug Minor   PackageOverlaps aem https://www.adobe.com/go/aem_cmcq_packageoverlaps_en

Reproduce Scenario (including but not limited to)

  1. Create a project based on archetype 27
  2. Include WKND as a 3rd party embed in all/pom.xml
  3. load code into a Cloud Manager pipeline
  4. Observe the two errors above

Platform and Version

  • A project with Archetype 27
  • WKND 1.0.0
@davidjgonzalez davidjgonzalez added bug Something isn't working enhancement New feature or request labels Aug 5, 2021
@davidjgonzalez
Copy link
Contributor

@gknobloch do you have a clean way of doing this?

My initial thought was repo init of course, but it seems unreasonable to try to model such a complex data structure there.

I dont think filters would work (since we want some replacement if ui.content.sample is installed; and even if not - that seems like it would get very complex quickly (hard for ppl to understand what's going on when looking at codebase as a reference).

We'd like to keep these base nodes in ui.apps in case someone doesn't want to install the full sample content.

Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants