AEM Pattern Detector issues

[JakeCham]

While upgrading to 6.5, we ran Pattern Detector tool and got below three issues.Any idea how to fix these issues?

1. message="The path: /apps/<...>/components/content/<...>/cq:dialog/content/items/column/items/<...>/items/well
violates content areas resource type usage internal path: /libs/granite/ui/components/foundation/well"

The pattern=CAV/content.area.violation was found by detector=ContentAccessDetector with

2.The path: /apps/<...>/components/content/<...>/cq:dialog/content/items/column/items/<....>/items/showHideContainer
violates content areas resource type usage internal path: /libs/granite/ui/components/foundation/well.

3. The path: /apps/<...>/components/content/<...>/cq:dialog/content/items/fieldset/items/column/items/popup violates content areas resource type usage internal path: /libs/granite/ui/components/foundation/well

/libs/granite/ui/components/coral/foundation/well/well.jsp is not anable in 6.5.Is that the cause to thses errors and how i fix that ?

[vanegi · Accepted solution]

Please go through the Sustainable Upgrade docs at [1]

[1] https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/sustainable-upgrade...

A content area violation (CAV) is detected because you are currently overriding or overlaying a node which is (or will be after the upgrade) in a "restricted area". You can read more about content areas here: https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/sustainable-upgrade...

To make a comparison: overlaying a node that is in a granite:internalArea is a bit like trying to extend a class which is marked as final in Java (ie: not allowed.