This is an AEM project set up with the wcm.io Maven Archetype for AEM.
To build the application run
mvn clean install
To build and deploy the application to your local AEM instance use these scripts:
build-deploy.sh
- Build and deploy to author instancebuild-deploy-publish.sh
- Build and deploy to publish instance
The first deployment may take a while until all updated OSGi bundles are installed.
After deployment you can open the application in your browser:
- Author: http://localhost:4502/hal
- Publish: http://localhost:4503/hal
You can deploy individual bundles or content packages to the local AEM instances by using:
mvn -Pfast cq:install
- Install and deploy bundle or content package to author instancemvn -Pfast,publish cq:install
- Install and deploy bundle or content package to publish instance
- Java 8
- Apache Maven 3.6.0 or higher
- AEM 6.5 author instance running on port 4502
- Optional: AEM 6.5 publish instance running on port 4503
- Include the Adobe Public Maven Repository in your maven settings, see wcm.io Maven Repositories for details.
- To obtain the latest service packs via Maven you have to upload them manually to your Maven Artifact Manager following these conventions for naming them.
It is recommended to set up the local AEM instances with nosamplecontent
run mode.
Modules of this project:
- parent: Parent POM with dependency management for the whole project. All 3rdparty artifact versions used in the project are defined here.
- bundles/core: OSGi bundle containing:
- Java classes (e.g. Sling Models, Servlets, business logic) with unit tests
- content-packages/apps-repository-structure: AEM content package defining root paths for application package validation
- content-packages/complete: AEM content package containing all OSGi bundles of the application and their dependencies
- config-definition: Defines the CONGA roles and templates for this application. Also contains a
development
CONGA environment for deploying to local development instances. - tests/integration: Integration tests running against the HTTP interface of AEM