Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

We upgraded our AEMasCS to Java21

Avatar

Community Advisor

4/7/25

AEM Discussions

We upgraded our AEMasCS to Java21  by Sarav Prakash


Overview

Sharing the steps followed, problems faced and fixes workarounds made.

 

https://medium.com/@bsaravanaprakash/we-upgraded-our-aemascs-to-java21-0c6b4a90f76d

 


Q&A

Please use this thread to ask questions relating to this article

4 Comments

Avatar

Level 9

4/23/25

Thanks for sharing

Avatar

Level 6

7/21/25

Thank you @sarav_prakash 

Avatar

Administrator

8/21/25

@sarav_prakash Really appreciate you documenting your team’s journey with the Java 21 upgrade. Posts like this save others a lot of trial and error. Reading through it made me wonder: if someone is planning their own upgrade, what’s the one pitfall you’d suggest they watch out for first, before anything else? Wondering what stood out to you as the biggest gotcha.

Avatar

Community Advisor

8/24/25

Hey @kautuk_sahni , thanks for feedback. Sure, slf4j was the biggest gotcha. After upgrade, blindly junits ll start to fail. Error trace not clear, developers would keep wondering why it fails. Just switching the deprecated library, no additional fixes required, all errors gets wiped off. It took sometime to chase this rootcause.

Other issues, developer can easily spot out and ll resolve.