AEM Quickstart JAR not compatible with JDK 17 | Community
Skip to main content
NageshRaja
NageshRaja
Level 5
September 12, 2024
Solved

AEM Quickstart JAR not compatible with JDK 17

  • September 12, 2024
  • 3 replies
  • 2055 views

Hey folks,

 

Why does the quickstart jar not work with JDK 17?

 

Loading quickstart properties: default
Loading quickstart properties: instance
java.lang.Exception: Quickstart does not run with newer versions as Java Specification 17 VM, but your VM (Java HotSpot(TM) 64-Bit Server VM / Oracle Corporation) reports java.specification.version=22
at com.adobe.granite.quickstart.base.impl.Main.checkEnvironment(Main.java:1056)
at com.adobe.granite.quickstart.base.impl.Main.<init>(Main.java:645)
at com.adobe.granite.quickstart.base.impl.Main.main(Main.java:980)
Quickstart: aborting

 

Is there any limitation on AEM not leveraging latest features from Java 17?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Rohan_Garg

Hi @nageshraja,

The AEM as a Cloud Service SDK should be built with a distribution and version of Java supported by Cloud Manager’s build environment. (Refer The AEM as a Cloud Service SDK)

Cloud Manager builds and tests your code using a specialised build environment.

Using a Specific Java Version

By default, projects are built by the Cloud Manager build process using the Oracle 8 JDK, but AEM Cloud Service customers are strongly advised to set the JDK version used to execute Maven to 11.

Simply put the JDK 17 is not supported by AEM!

Hope this helps!

3 replies

MukeshYadav_
Community Advisor
MukeshYadav_Community Advisor
Community Advisor
September 12, 2024

Hi,

All version are not supported, you may refer document for version compatibility https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements#java-virtual-machines

Thanks

    Rohan_Garg
    Community Advisor
    Rohan_GargCommunity AdvisorAccepted solution
    Community Advisor
    September 12, 2024

    Hi @nageshraja,

    The AEM as a Cloud Service SDK should be built with a distribution and version of Java supported by Cloud Manager’s build environment. (Refer The AEM as a Cloud Service SDK)

    Cloud Manager builds and tests your code using a specialised build environment.

    Using a Specific Java Version

    By default, projects are built by the Cloud Manager build process using the Oracle 8 JDK, but AEM Cloud Service customers are strongly advised to set the JDK version used to execute Maven to 11.

    Simply put the JDK 17 is not supported by AEM!

    Hope this helps!

      Tad_Reeves
      Adobe Champion
      Tad_ReevesAdobe Champion
      Adobe Champion
      September 12, 2024

      Additionally you should keep your eye peeled for this session at AdaptTo() at the end of October: https://adapt.to/2024/schedule/aem-65-and-java-17

       

      AEM only supported JDK8 up to 6.5, and now only supports JDK8 and JDK11.  Making AEM support JDK17 will likely result in an entirely new version of AEM to differentiate between what works on prior JDKs and what has features deprecated so that it works on JDK17.

        Terms & ConditionsAccessibility statement

        Loading footer...