Skip to main content

Create AEM Project using Maven Archetype 11

Let's start with our journey of Adobe Experience Manager project development.

I am using AEM 6.3, Java 1.8 and Maven 3.2.

Follow below steps and try to replicate the same at your end. Let know of any issues if you face in the comment section.


  1. Go to your project path and validate the commands mvn -v and java -version are pointing to the accurate installation of Maven and JDK.
  2. Type below command to start: "mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=11 -DarchetypeCatalog=https://repo.adobe.com/nexus/content/groups/public/"
  3. Once this is done downloading the dependency and starts creating folder structure, it will ask you for the required information. You can refer below information that I have given, you need to use yours based on your requirement or client need. 
Define value for property 'groupId': : first-project-aem
Define value for property 'artifactId': : first-project-aem
Define value for property 'version':  1.0-SNAPSHOT: :
Define value for property 'package':  first-project-aem: : com.blogspot.curiousjava
Define value for property 'appsFolderName':  first-project-aem: :
Define value for property 'artifactName':  first-project-aem: :
Define value for property 'componentGroupName':  first-project-aem: : Set 1
Define value for property 'contentFolderName':  first-project-aem: : first-project
Define value for property 'cssId':  first-project-aem: : first-project
Define value for property 'packageGroup':  first-project-aem: : first-project
Define value for property 'siteName':  first-project-aem: : curious-java-aem
Once you are done with above, it will ask you for confirmation. Press "Y" and you are ready to start your journey to AEM-6.3. You can import the project in your IDE and start working towards your project.

Best of luck with your start to AEM learning, hope this helps. 
Labels:

Popular posts from this blog

Overview of EJB and Lifecycle

The container is responsible for loading, activating, and in general maintaining the "life-cycle" of objects it provides. EJB have a fairly complex life-cycle. There are several kinds of EJB: Session Beans: These may be either stateful or stateless, and are primarily used to encapsulate business logic, carry out tasks on behalf of a client, and act as controllers or managers for other beans.   Entity Beans: Entity beans represent persistent objects or business concepts that exist outside a specific application's lifetime. They are typically stored in a relational database. Entity beans can be developed using bean-managed persistence, which is implemented by the developer, or container-managed persistence, implemented by the container.   Message-Driven Beans : Message-driven beans listen asynchronously for Java Message Service (JMS) messages from any client or component and are used for loosely coupled, typically batch processing.
Read more

Singleton Pattern

Lazy Initialization :- The instantiation of an object can be delayed until it is actually needed. Usage: This especially beneficial when the constructor is doing a costly job like, accessing a remote database. Example: This code demonstrates how the Singleton pattern can be used to create a counter to provide unique sequential numbers, such as might be required for use as primary keys in a Database:   Sequence.java   public class Sequence { private static Sequence instance; private static int counter; private Sequence() { counter = 0; // May be necessary to obtain // starting value elsewhere... } public static synchronized Sequence getInstance() { if(instance==null) // Lazy instantiation { instance = new Sequence(); } return instance; } public static synchronized int getNext() { return ++counter; } }   Some things to note about this implementation: Synchronized methods are used to ensure that the class is thread-safe. This class cannot be subclassed because the constructor is private ...
Read more

Hibernate Notes

  The Hibernate project has the structure as shown in the figure as above. We need one hibernate.cfg.xml file for hibernate configuration which handles connection pulling and other stuff like driver name, username of the database, password of the database, and the following properties.. Hibernate.cfg.xml <?xml version='1.0' encoding='utf-8'?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory>   <property name="hibernate.connection.driver_class"> com.mysql.jdbc.Driver</property>   <property name="hibernate.connection.url"> jdbc:mysql://localhost/hibernatetutorial </property>   <property name="hibernate.connection.username"> root </property>   <property name="hibernate.connection.password"></pr...
Read more