aem-project-archetype

This release includes the following enhancements and new features:

• React & Angular (SPA editor)

  • Server Side Rendering support (+IO runtime for React)
  • Experience Fragment support
  • Lazy-Loading / Code splitting examples provided
  • Various fixes (Container, Navigation Routing)

• Various bug fixes & Updates

• Commerce Integration Framework

  • Navigation component based on WCM Core Component
  • Content Fragment Commerce Component

• AEM Analyser Maven Plugin
  Update aemanalyser-maven-plugin to version 1.0.10

• Dispatcher configuration

  • Dispatcher configs for cloud include opt-in marker for direct source mode to be enabled by default
  • Dispatcher config immutable files for cloud synchronized with latest Dispatcher SDK
  • Allow video formats to be downloadable in dispatcher module config filters for cloud
  • Setting that adds User-Agent to vary header removed

• Project structure

  • name property added in parent pom.xml

For a list of all issues fixed, see Archetype 28 milestone.

Contributors

We would like to thank the following contributors that made this release possible:
External Contributors
Mansi Agrawal, Hanish Bansal, Mark J. Becker, David Bosschaert, Cezary Czernecki, Justin Edelson, Namit Gupta, Cedric Huesler, Christophe Jelger, Krystian Nowak, Ravi Kiran Papani, Pankaj Parashar, Niek Raaijmakers, Levente Sántha, Sharanya Vinod

Core Team
Bartosz Glowacki, Burkhard Pauli, Mirko Sagolj, Jean-Christophe Kautzmann, Vlad Bailescu

This release includes the following enhancements and new features:

• Generate a minimum but complete CIF project
  If commerce is enabled the archetype generates now a minimum but complete CIF project

• New templates for remote SPA editing
  Two new page components have been introduced via spa-project-core to enable editing of externally hosted React SPA/Next.js app within AEM

• SPA core components
  Core components are now added to the react and angular frontend to provide a good example how to use them

• Adaptive forms theme and templates
  Example templates for adaptive forms are added to the project if forms support is enabled

• Improvement of the UI test module
  Add retry mechanism to reduce flakiness and update of the Webdriver IO depedency

• Update of core dependencies
  Updated to latest AEM core components 2.15.2, core forms components 0.0.22, SPA project core 1.2.8

For a list of all issues fixed, see Archetype 27 milestone.

Contributors

We would like to thank the following contributors that made this release possible:
External Contributors
Sakshi Arora, David Bosschaert, Guillaume Clement, David Catalan, Kyle Giovannetti, Viresh Gupta, Markus Haack, Kaushal Mall, Jean-Pierre Matsumoto, Zoran Nikolovski, Niek Raaijmakers, Douglas Ross, Levente Sántha, Tomasz Sobczyk, Benjamin Solum, Sharanya Vinod, Konrad Windszus, Jason Wolf
Core Team
Bartosz Glowacki, Burkhard Pauli, Mirko Sagolj, Jean-Christophe Kautzmann, Vlad Bailescu

This is an emergency hotfix release. It only contains the update of the aemanalyser plugin. The old version causes build problems with the latest cloud SDK. For more information see the related issue at https://github.com/adobe/aem-project-archetype/issues/638

This release includes the following enhancements and new features:

• Support AEM Analyser:
  AEMaaCS provides an extended analysis of projects in the build and deployment pipeline. This includes running the Feature Model Analysers on the content packages. AEM project now includes an analyzer maven plugin that locally validates the content packages from the current project. It helps find issues with these before the packages are deployed into AEMaaCS, by running additional validation locally as part of the Maven build.

• Forms Integration Framework:
  Options to include latest AEM Forms Core Components and AEM Forms as a Cloud Service SDK specific configurations to an AEM Archetype project. It helps you build a ready-to-use project for AEM Forms as a Cloud Service SDK.

• Core Components 2.13.0:
  Benefit from the latest update to our many of our components, including new support for Dynamic Media in the image component, a new Form POST handler to submit JSON to any https URL, include custom CSS/JS/metadata in page component using CS config, utility class to simplify data layer integration for custom components.

• SPA Core 1.2.0:
  Introduces a new RemotePage component, for enabling editing of remotely hosted React SPAs.

For a list of all 11 issues fixed, see Archetype 25 milestone.

Contributors

We would like to thank the following contributors that made this release possible:

External Contributors
Markus Haack, Levente Sántha, Krystian Panek

Core Team
Vlad Bailescu, Christophe Jelger, Mirko Sagolj, Artur Kudlacz, Burkhard Pauli, Patrick Fauchere, David Bosschaert, Oleksandr Borysyuk, Rishi Mehta, Sharanya Vinod, David Catalan, Jörg Hoh

This release includes the following enhancements and new features:

• Adobe Client Data Layer:
  Option to enable the ACDL event-driven data layer, which standardizes how the page data and events are exposed and can be sent to digital analytics and reporting servers.

• Accelerated Mobile Pages:
  Option to enable AMP support, which will make pages load blazingly fast when accessing them from Google search results.

• Commerce Integration Framework:
  Option to includes the latest CIF Core Components and everything else you need to kickstart your Commerce projects. For a complete sample project based on the AEM Project Archetype, have a look at our Venia storefront.

• Core Components 2.11.0:
  Benefit from the latest update to our components, including the new PDF Viewer and ProgressBar components.

• Client Library Extensions:
  Extended capabilities to load client libraries with attributes like async or embed, or to inline the CSS or the JS into the page.

• Selenium-based UI testing project:
  A ready-to-use project to start testing the UI of your AEM on-prem and AEMaaCS applications. It relies on Webdriver.IO automation test framework. It also includes basic tests for the sample application.

• Integration Testing:
  This allows running integration tests that exercise the capabilities of AEM via HTTP calls to its API. The integration tests in this archetype use the AEM Testing Clients and showcase some recommended best practices to be put in use when writing integration tests for AEM.

For a list of all 76 issues fixed, see Archetype 24 milestone.

Contributors

We would like to thank the following contributors that made this release possible:

External Contributors
Austen Wade, Bartosz Borowski, Cezary Czernecki, Christophe Jelger, David Catalan, duchauha, Daniel Platon, Francesco Mari, Daniel Gordon, Mark J. Becker, Jim Frenette, Markus Hack, Niek Raaijmakers, Rachit Kumar, Robert Munteanu, Stefan Seifert, Sushant Bhasin, thinkstainless

Core Team
Andreea Dracea, Bartosz Glowacki, Burkhard Pauli, Mirko Sagolj, Jean-Christophe Kautzmann, Richard Hand, Vlad Bailescu

This release includes the following enhancements:

• AEM as a Cloud Service support:
  Everything is now ready for your new project to go the cloud: the dispatcher configuration is cloud-ready, the project structure is as it should be, and we've added support for the cloud SDK that replaces the Uber-Jar.
• SPA Editor support:
  So that you can also implement your site with a JS framework like React or Angular, we've merged the "SPA Archetype" into this one, and we took the opportunity to improve it.
• Cleaned-up example content with basic styling:
  We've streamlined the sample content to be as simple as it can be: a localized experience fragment with a style applied by the Style System makes the page header and footer, and the front-end build process defines a minimalistic slick look to start off.
• Simplified archetype variables:
  So that you don't get asked a dozen obscure questions, we reduced the questions asked by the archetype. Typically, the same appId variable will determine the names of the app, conf and content folders.
• Core Components 2.8.0 support:
  Benefit from the latest update to our components that provides enhancements to the following components: Content Fragment, Experience Fragment, Download, Embed, Image, and Navigation.

For a list of all the 21 issues fixed, see the Archetype 23 milestone.

Contributors

We would like to thank the following contributors that made this release possible:

External Contributors
Bryan Stopp, Daniel Gordon, David Gonzalez, Dominik Hardtke, Jim Matheson, jtriemstra, Samuel Meuli

Core Team
Andreea Dracea, Bartosz Glowacki, Burkhard Pauli, Mirko Sagolj, Jean-Christophe Kautzmann, Richard Hand, Vlad Bailescu

• Frontend module contains static web server for faster development
• Default value for country_language property
• Bunch of smaller bug fixes. For a complete list please have a look to the milestone 22 issues.

Contributors

We would like to thank the following contributors that made this release possible:

External Contributors
Guillaume Clement, Daniel Gordon, haktober, Jörg Hoh, Robin KM, Suren Konathala, Evgeny Tugarev

Core Team
Andreea Dracea, Burkhard Pauli, Mirko Sagolj, Jean-Christophe Kautzmann, Richard Hand, Vlad Bailescu

• Includes Core Components 2.7.0 and proxies for new components: Experience Fragment, Embed
• Updates content structure to enable choosing between single and multi-site projects
• Adds header and footer based on localised experience fragments
• Adds dispatcher module
• Updates modules
• Improves ui.frontend build and documentation.

For further changes please have a look to the milestone 21 issues.

Contributors

We would like to thank the following external contributors that made this release possible:
Daniel Gordon, Brian Stopp, Gregg Thomason, Tiffany Olejnik, Harold Putman, Austen Wade

• Includes Core Components 2.5.0 and proxies for newly added components
• Adds dedicated frontend module based on webpack with support for SASS for CSS and Typescript for JS generation
• Includes default CSS selectors for AEM Core Components
• Replaces maven-bundle-plugin with bnd-maven-plugin

For further changes please have a look to the milestone 20 issues.

Contributors

We would like to thank the following contributors that made this release possible:

External Contributors
Daniel Gordon, Jim Matheson, Stefan Seifert

Core Team
Burkhard Pauli, Richard Hand

• Updated to wcm-core-components v2.4.0

• Target AEM version can be set with the argument optionAemVersion
• Tests are based on JUnit5
• Generated project is compatible to JDK 11
• Custom error handler for 404 responses can be added with the new argument optionIncludeErrorHandler

For further changes please have a look to the milestone 18 issues.

Changes

• Updated to wcm-core-components v2.3.0

For further changes please have a look to the milestone 17

Requirements

• AEM 6.4.2.0 or
• AEM 6.3.3.0

Changes

Please have a look to the milestone 16

Requirements

• AEM 6.4.2.0 or
• AEM 6.3.3.0

Changes

Please have a look to the milestone 15

Requirements

• AEM 6.4.2.0 or
• AEM 6.3.3.0

Changes

Please have a look to the milestone 14

Requirements

• AEM 6.4 or
• AEM 6.3 + SP2

Changes

• updated to wcm-core-components v2.0.4

Requirements

• AEM 6.4 or
• AEM 6.3 + SP2

Notable improvements:

• use AEM 6.3 API - #94
• includes AEM Core WCM Components #102

Minor feature update targeting AEM 6.2 or newer.

Notable improvements:

• use AEM 6.2 API - #64
• uses the new OSGi R6 annotations by default - #84 , #85
• plugin and dependency updates - #82, #80, #79 , #69 , #49

Notable bug fixes:

• bundle was not uninstalled when uninstalling the content package - #62
• various integration testing fixes - #77, #70, #49, #38
• bundle installation was failing- #56

Bugfix release

• #35 - mvn install fails in generated project

The version 9 of the AEM project archetype brings incremental improvements and bug fixes. The archetype has been tested on AEM 6.0 and is expected to work properly on the upcoming 6.1 version.

• Sling Models support ( #19 )
• support Maven 3.3.1 ( #31)
• simplify contribution ( #18 )
• various fixes and cleanups