You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
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.
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!
Reproduce Scenario (including but not limited to)
Platform and Version
The text was updated successfully, but these errors were encountered: