Demo code for talk at adaptTo() 2019:
https://adapt.to/2019/en/schedule/assets-and-links-in-aem-projects.html
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 sample content page in your browser:
- Author: http://localhost:4502/editor.html/content/assetlinksdemo/en.html
- Publish: http://localhost:4503/content/assetlinksdemo/en.html
- JDK 1.8
- Apache Maven 3.5.2 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.
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 with Java classes (e.g. Sling Models, Servlets, business logic).
- content-packages/ui.apps: AEM content package containing:
- AEM components with their scripts and dialog definitions
- HTML client libraries with JavaScript and CSS
- i18n
- content-packages/complete: AEM content package containing all OSGi bundles of the application and their dependencies
- content-packages/conf-content: AEM content package with editable templates stored at
/conf - content-packages/sample-content: AEM content package containing sample content (for development and test purposes)
- config-definition: Defines the CONGA roles and templates for this application. Also contains a
developmentCONGA environment for deploying to local development instances.