Hi all,
I am downloading aem-guides-wknd with the below 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=39 \
-D appTitle="WKND Sites Project" \
-D appId="wknd" \
-D groupId="com.adobe.aem.guides" \
-D artifactId="aem-guides-wknd" \
-D package="com.adobe.aem.guides.wknd" \
-D version="0.0.1-SNAPSHOT" \
-D aemVersion="6.5"
Where is AEM Archetype coming in to picture here?
Do I have to download AEM Archetype first and run the above command for WKND Sites Project?
Or the above command for WKND Sites Project internally contains AEM Archetype and so no need to download AEM Archetype separately?
Also What does -D archetypeVersion=39 in the above command indicate?
Appreciate all your replies.
Thanks,
RK.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @nsvsrk ,
The command you shared is used to generate a new multi module Maven project for AEM from scratch.
If you want to get 'WKND Sites Project' sample project, you can get it from GIT
While generating a new project, maven uses the archetypeVersions mention in the command and based on that the new Project structure would be generated (based on archetype the project structure varies in terms of folders structure, features ..etc)
Thanks,
Raju.
Hi @nsvsrk ,
Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Hi,
The command you're using is meant to create a new archetype—a project skeleton—for your own AEM project. In contrast, the WKND project is a fully developed reference implementation.
The -DarchetypeVersion=39
flag specifies which version of the archetype you want to use. Archetypes evolve over time—files may be reorganized, initial content and configurations updated—so specifying a version lets you target a specific state. In most cases, it's fine to use the latest available version.
If you're interested in exploring the full WKND project code, you can download or clone it from GitHub: https://github.com/adobe/aem-guides-wknd
Hope this helps!
1. What’s the AEM Archetype?
The AEM Project Archetype is a Maven template that creates a fresh AEM project with best practices.
You don’t download it manually — Maven pulls it automatically.
2. What Your Command Does
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=39 \
-D appTitle="WKND Sites Project" \
-D appId="wknd" \
-D groupId="com.adobe.aem.guides" \
-D artifactId="aem-guides-wknd" \
-D package="com.adobe.aem.guides.wknd" \
-D version="0.0.1-SNAPSHOT" \
-D aemVersion="6.5"
This generates a new AEM project scaffold using archetype version 39, not the actual WKND repo.
It just names your project “WKND Sites Project.”
3. Do You Need to Download the Archetype First?
Nope, not at all.
-> Maven fetches it automatically from Adobe/Maven Central.
4. What Does -D archetypeVersion=39 Mean?
It tells Maven which version of the archetype template to use.
39 = a stable archetype release for AEM 6.5 and AEMaaCS.
5. When to Use Each Option
Use Maven Archetype, when you want to create your own project with WKND-like structure.
Clone WKND from GitHub, when you want the official WKND sample project for learning/demo.
Hope this helps
- Brian Li
Thanks @BrianKasingli .
I want to mark this answer as Correct, but do not see the option.
Thanks,
RK.
Views
Replies
Total Likes
Views
Likes
Replies