Expand my Community achievements bar.

SOLVED

Pattern Detector from AEM 6.2 to 6.5

Avatar

Level 1

Hi all,

I am planning to upgrade 6.2 to 6.5. Just want to estimate how much effort need in code merging. May I know is there any package/Pattern Detector to identify the deprecated api, code , function from 6.2 for 6.5.

 

Thank you all.

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Aries 

 

Yes you can use the Pattern Detector tool which is provided by Adobe.

This feature allows you to check existing AEM instances for their upgradability by detecting patterns in use that:

  1. Violate certain rules and are done in areas that will be affected or overwritten by the upgrade
  2. Use an AEM 6.x feature or an API that is not backwards compatible on AEM 6.5 and can potentially break after upgrade.

You can download it from here:

https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/...

and it should be installed on your Source instance i.e. 6.2 AEM instance.

 

Thanks!

View solution in original post

2 Replies

Avatar

Community Advisor

@Aries Please refer to below documentation URL:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/pattern-detector.h...

The Pattern Detector is released separately as a one package working on any source AEM versions from 6.1 to 6.5 targeting AEM 6.5 upgrade. It can be installed using the Package Manager.

Avatar

Correct answer by
Community Advisor

Hi @Aries 

 

Yes you can use the Pattern Detector tool which is provided by Adobe.

This feature allows you to check existing AEM instances for their upgradability by detecting patterns in use that:

  1. Violate certain rules and are done in areas that will be affected or overwritten by the upgrade
  2. Use an AEM 6.x feature or an API that is not backwards compatible on AEM 6.5 and can potentially break after upgrade.

You can download it from here:

https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/...

and it should be installed on your Source instance i.e. 6.2 AEM instance.

 

Thanks!