We upgraded our AEMasCS to Java21 | Adobe Higher Education
Skip to main content
sarav_prakash
Community Advisor
sarav_prakashCommunity Advisor
Community Advisor
April 8, 2025

We upgraded our AEMasCS to Java21

  • April 8, 2025
  • 4 risposte
  • 411 visualizzazioni
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 risposte

    Hemant_arora
    Hemant_arora
    Level 8
    April 24, 2025

    Thanks for sharing

      Uppari_Ramesh
      Uppari_Ramesh
      Level 5
      July 21, 2025

      Thank you @sarav_prakash 

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        August 21, 2025

        @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.

        Kautuk Sahni
        sarav_prakash
        Community Advisor
        sarav_prakashCommunity AdvisorAutore
        Community Advisor
        August 25, 2025

        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. 

          Termini e CondizioniAccessibility statement

          Loading footer...