AEM Pattern Detector Interpretation

Avatar

Avatar

Sergei_P2018

Avatar

Sergei_P2018

Sergei_P2018

20-06-2019

Hi all

We're analyzing the output of the Pattern Detector and some of the violations seems strange.

1. Non-Backwards Compatible Changes

For instance, we getting:

The content stored at /apps/<...>/cq:dialog/content/items/section3/items/column/items/details-group/items/details by including (sling:resourceType) the JCR path at /libs/cq/gui/components/authoring/dialog/richtext might be incompatible after update and might need some adaption

We would like to learn more about the severity of this issue, like what type of change is expected? Is there a backward compatible alternative for richtext, for instance?

2. Content Area Violation

For instance, we getting:

The content stored at /apps/<...> by overriding (sling:superResourceType) the JCR path at /libs/cq/workflow/components/model/process might be incompatible after update and might need some adaption

However /libs/cq/workflow/components/model/processis is explicitly marked as granite:PublicArea which is safe for that type of actions.

If anyone has answers, please share.

Thanks in advance!

View Entire Topic

Avatar

Avatar

Sergei_P2018

Avatar

Sergei_P2018

Sergei_P2018

26-06-2019

Hi Joerg Hoh

We use pd-all-aem65-0.10 package and the upgrade is taking place from 6.4.3 to 6.5.0