Maven AEM Project Archetype 23 was recently released. To use, setup your local development environment for AEM as a Cloud Service SDK or use one of the followimg AEM versions: 6.5.0+, 188.8.131.52+ or 184.108.40.206+. Additonally, Java 8 or 11 and Maven 3.3.9+ is also required. Here is an overview of a few of the changes.
The number of prompts for property values when generating the project has been reduced. By default,
artifactId will use the
appId value and
package will use the
groupId value. You can change these to use different values if you prefer by adding them to your generate command line.
This is a minimal example for batch mode project generation:
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 Project" \ -D appId="myproject" \ -D groupId="com.myproject" \ -D frontendModule=general \ -D includeExamples=n
|appTitle||For website title and component groups|
|appId||For app, conf and content folder names; clientlib names|
||Base Maven artifact ID|
|groupId||Base Maven group ID|
||Java Source Package|
||Target AEM version (can be
||Includes a dispatcher configuration either for cloud or for AMS/on-premise, depending of the value of
||Includes a Webpack frontend build module that generates the clientlibs (
||Language and country code to create the content structure from (e.g.
||Includes a language-master content structure (
||Includes a Component Library example site (
||Includes a custom 404 response page that will be global to the entire instance (
React and Angular Support
The AEM SPA Project Archetype has been merged into this version to facilitate a React or Angular Single Page App that implements the SPA Editor.
- Styling updated for example content
- Responsivegrid replaced with core container component
- Experience fragment simplified for the header and footer
- Custom helloworld component updated
Example Content Page
Other Changes Include
- Support added for AEM as a Cloud Service SDK
- Mapping / rewrite rules to support the image core component. For example, when using the dispatcher module with the associated Resource Resolver Factory rewrite rule, images referenced in
org.apache.sling.servlets.annotationsdependency management added
- use Sling’s
org.apache.sling.bnd.models.ModelsScannerPluginwhich automatically identifies and registers
SlingModelsin the project.
repository-structureproject renamed to
Part 3 of 3 in the AEM Maven Project series.
Part 1 | Adobe Experience Manager (AEM) Maven Project Part II