Install service pack without recompiling artefacts aganist corresponding uber jar

Avatar

Avatar

ashissharma619

Avatar

ashissharma619

ashissharma619

07-08-2020

Is it okay to upgrade the AEM with 6.5.5 service pack and keep the artefacts compiled against 6.5.0 itself. We tested functionally and there are no issues. Is there a mandatory requirement that all artefacts on the instance needs to be compiled against the same version.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K
Jörg_Hoh
Employee

07-08-2020

In many cases this approach works. But there are cases, where API changes are introduced (typically for security reasons), which make bundle imports not working anymore. But that's something you can find out very easily. But evn in that case I would suggest that update to the matching uber.jar asap.

 

Jörg

Answers (1)

Answers (1)

Avatar

Avatar

vanegi

Employee

Avatar

vanegi

Employee

vanegi
Employee

07-08-2020

Hi @ashissharma619,

When you need to recompile, the first thing to do is update your project to reference the AEM UberJar. As documented on https://docs.adobe.com/content/help/en/experience-manager-65/developing/devtools/ht-projects-maven.h..., the UberJar is available in two different versions:

  • An obfuscated version which is freely available on repo.adobe.com.
  • An unobfuscated version which can only be obtained by licensed customers and partners through Adobe Support.

There are a variety of cases when you need the unobfuscated version – certain types of unit tests, certain Declarative Services use cases, etc. These are laid out in the documentation. If you were using the obfuscated version before, you can continue to use the obfuscated version. And if you needed the unobfuscated version, you still need it.

 

I would recommend to go with exact uber-jar version matching with AEM. Adobe recommends deploying against the Uber Jar that ** does not **contain the deprecated APIs to make sure that your applications will run properly on future versions of AEM.

 

Thanks!!