AEM 6.5 archetype 23 is not working | Community
Skip to main content
S
shrutimu
June 22, 2025
Solved

AEM 6.5 archetype 23 is not working

  • June 22, 2025
  • 3 replies
  • 1060 views

Hi everyone,

I'm encountering an issue while trying to create an AEM project named "Mysite" using version 6.5.0 and archetype 23. The build fails with the message: "Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.4.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist." I've checked the archetype versions on https://github.com/adobe/aem-project-archetype/blob/develop/VERSIONS.md  for reference.

Could you please suggest a solution?

Here's the command I'm using:

mvn -B archetype:generate -D archetypeGroupId=com.adobe.granite.archetypes -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=23 -D aemVersion=6.5.0 -D appTitle="My Site" -D appId="mysite" -D groupId="com.mysite" -D frontendModule=general -D includeExamples=n

Best answer by SantoshSai

@shrutimu 

To set up a new AEM project using Adobe’s official Maven Archetype, you can use the following command (make sure you have Java 11+ and Maven installed):

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.3.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=54 \
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite"

This will generate a full AEM project structure with core, UI, content, and dispatcher modules.
Reference: AEM Project Archetype GitHub

Additional Notes:
If you're using AEM as a Cloud Service (AEMaaCS):

  • No need to manually install service packs.

  • Make sure your archetype version is the latest (e.g., 54 or whatever is current).

  • Your builds should deploy to Cloud Manager.

If you're using AEM On-Premise (6.5.x):

  • Make sure you install the latest AEM Service Pack corresponding to your base version.

  • You may need to adapt the archetype version slightly (e.g., older versions of the archetype are more aligned with older AEM).

You can always check compatibility and setup details here:
https://github.com/adobe/aem-project-archetype

 

3 replies

DPrakashRaj
Community Advisor
DPrakashRajCommunity Advisor
Community Advisor
June 22, 2025

Are you trying to create maven archetype on personal pc or your company computer. If you are on company computer you might be blocked with company proxy policies that might be blocking the download from https://github.com/adobe/aem-project-archetype/blob/develop/VERSIONS.md and I believe you might to update your maven command.its always recommended to use the latest maven archetype.

https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/project-setup

sample command

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
    -D archetypeGroupId=com.adobe.aem \
    -D archetypeArtifactId=aem-project-archetype \
    -D archetypeVersion=20 \
    -D appTitle="My Project" \
    -D appId="my-project" \
    -D groupId="com.my.project" \
    -D artifactId="my-project" \
    -D package="com.my.project" \
    -D version="0.0.1-SNAPSHOT" \
    -D aemVersion="6.5.0"

 

    SantoshSai
    Community Advisor
    SantoshSaiCommunity Advisor
    Community Advisor
    June 22, 2025

    Hi @shrutimu,

    The error you're encountering:

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.4.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.adobe.granite.archetypes:aem-project-archetype:23)

    happens because although version 23 of the AEM archetype does exist, it lacks the necessary metadata (archetype-metadata.xml) required by the Maven archetype plugin to generate a project.

    You can verify that version 23 exists here:
    https://repo1.maven.org/maven2/com/adobe/granite/archetypes/aem-project-archetype/23/

    However, if you download the .jar file and inspect it, you'll see that it's missing the internal META-INF/maven/archetype-metadata.xml file — which is why Maven cannot use it to generate a new project.

    Solution: Use a newer working version

    Instead, use version 41, which is fully supported and includes all necessary metadata.

    Here’s a working command:

    mvn -B archetype:generate \
  -DarchetypeGroupId=com.adobe.granite.archetypes \
  -DarchetypeArtifactId=aem-project-archetype \
  -DarchetypeVersion=41 \
  -DarchetypeCatalog=internal \
  -DaemVersion=6.5.0 \
  -DappTitle="My Site" \
  -DappId=mysite \
  -DgroupId=com.mysite \
  -DfrontendModule=general \
  -DincludeExamples=n

    You can browse all available versions here:
    https://repo1.maven.org/maven2/com/adobe/granite/archetypes/aem-project-archetype/

    Santosh Sai
      S
      shrutimuAuthor
      June 23, 2025

      Hi @santoshsai ,

      I'm new to AEM and trying to learn through self-learning. I've tried executing the command you provided, but I'm still encountering the same errors.

      Are the following versions compatible?

      • Java version: 15.0.1

      • Apache Maven 3.9.9

      SantoshSai
      Community Advisor
      SantoshSaiCommunity AdvisorAccepted solution
      Community Advisor
      June 23, 2025

      @shrutimu 

      To set up a new AEM project using Adobe’s official Maven Archetype, you can use the following command (make sure you have Java 11+ and Maven installed):

      mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.3.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=54 \
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite"

      This will generate a full AEM project structure with core, UI, content, and dispatcher modules.
      Reference: AEM Project Archetype GitHub

      Additional Notes:
      If you're using AEM as a Cloud Service (AEMaaCS):

      • No need to manually install service packs.

      • Make sure your archetype version is the latest (e.g., 54 or whatever is current).

      • Your builds should deploy to Cloud Manager.

      If you're using AEM On-Premise (6.5.x):

      • Make sure you install the latest AEM Service Pack corresponding to your base version.

      • You may need to adapt the archetype version slightly (e.g., older versions of the archetype are more aligned with older AEM).

      You can always check compatibility and setup details here:
      https://github.com/adobe/aem-project-archetype

       

      Santosh Sai
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        June 23, 2025

        @shrutimu Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you.

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...