The Core Components are designed to be flexible and compatible with all supported AEM versions. Because of this a release of the components can contain multiple versions of the same component.
The following tables illustrate the compatibility of the releases of the Core Components along with which component versions are contained in which releases.
The following table, the contents of which are available on GitHub with full release details, gives an overview of the releases of the Core Components and their compatibility with AEM releases and Java versions.
|Release||Description||AEM 6.4||AEM 6.5||AEM as a Cloud Service||Java||Release Date|
|2.15.0||This release includes support for progressive web apps in the Page Component and supports version 2.0.0 of the Adobe Data Layer.||188.8.131.52+ *||184.108.40.206+ *||Continual||8, 11||23 February 2021|
|2.14.0||This release includes new options for the Embed Component and introduces the Brand Slug at the page level as well as addressing many issues.||220.127.116.11+ *||18.104.22.168+ *||Continual||8, 11||9 February 2021|
|2.13.2||This was a patch release addressing an issue with the RTE when used on AEMaaCS||22.214.171.124+ *||126.96.36.199+ *||Continual||8, 11||16 December 2020|
|2.13.0||This release includes new Dynamic Media features for the Image Component.||188.8.131.52+ *||184.108.40.206+ *||Continual||8, 11||4 December 2020|
|2.12.2||This was a patch release for 2.12.0 including minor fixes.||220.127.116.11+ *||18.104.22.168+ *||Continual||8, 11||11 November 2020|
|2.12.1||This was a patch release for 2.12.0 that fixes a major bug in the Image Component.||22.214.171.124+ *||126.96.36.199+ *||Continual||8, 11||5 November 2020|
||188.8.131.52+ *||184.108.40.206+ *||Continual||8, 11||29 October 2020|
|2.11.0||This release introduced AMP support.||220.127.116.11+ *||18.104.22.168+ *||Continual||8, 11||20 July 2020|
|2.10.0||This release introduced the PDF Viewer component.||22.214.171.124+||126.96.36.199+||Continual||8, 11||17 June 2020|
|2.9.0||This release enabled integration with the Adobe Client Data Layer and introduced the Progress Bar component.||188.8.131.52+||184.108.40.206+||Continual||8, 11||29 May 2020|
|2.8.0||This release focused on fixes with small enhancements.||220.127.116.11+||18.104.22.168+||Continual||8, 11||5 December 2019|
|2.7.0||This release introduced the new Embed component.||22.214.171.124+||126.96.36.199+||Continual||8, 11||25 September 2019|
|2.6.0||This release introduced the new Experience Fragment component.||188.8.131.52+||184.108.40.206+||Continual||8, 11||6 September 2019|
|2.5.0||This release introduced the new Accordion, Button, Container, and Download components.||220.127.116.11+||18.104.22.168+||Continual||8, 11||25 June 2019|
|2.4.0||This release introduced the Content Fragment List Component.||22.214.171.124+||126.96.36.199+||Continual||8, 11||7 May 2019|
|2.3.2||This release focused on refinements to the Component Library, but also contains some feature enhancements for the Separator Component.||188.8.131.52+||184.108.40.206+||Continual||8||14 March 2019|
|2.3.0||This release focused on the Component Library as well as introducing the new Separator Component, but also contains some feature enhancements for the Image Component.||220.127.116.11+||-||-||8||11 February 2019|
|2.2.2||This release mainly focused on bug fixes, but also contains some feature enhancements for the Carousel Component.||18.104.22.168+||-||-||8||27 November 2018|
|2.2.0||This release introduced the Tabs Component and the Carousel Component as well as improvements to the Image Component, Page Component, and Title Component and enhanced tracking.||22.214.171.124+||-||-||8||16 October 2018|
|2.1.0||This release introduced the Teaser Component along with improvements to the Image Component and numerous bug fixes.||126.96.36.199+||-||-||8||13 July 2018|
|2.0.8||This was a bugfix release.||188.8.131.52+||-||-||8||12 June 2018|
|2.0.6||This release added under-the-hood improvements, bug fixes, and small improvements including support of image flip in the Image Component.||184.108.40.206+||-||-||8||11 April 2018|
|2.0.4||This release mostly focussed on under-the-hood improvements, bug fixes, plus some minor improvements to the Image Component, Page Component, and Content Fragment Component.||220.127.116.11+||-||-||8||7 March 2018|
|2.0.0||This release introduced the Navigation Component, Language Navigation Component, and the Quick Search Component and implemented the Style System for all components.||18.104.22.168+||-||-||8||16 January 2018|
|1.1.0||This release implements JSON export on all components and introduces the Content Fragment Component.||22.214.171.124+||-||-||8||10 October 2017|
|1.0.6||This release adds several fixes for the Image Component.||126.96.36.199+||-||-||8||4 August 2017|
|1.0.4||This release adds fixes for the Page Component, Image Component, and various global fixes and improvements.||188.8.131.52+||-||-||8||26 April 2017|
|1.0.2||This release adds fixes for animated GIF images in Image Component.||184.108.40.206+||-||-||7||22 March 2017|
|1.0.0||Initial release of Core Components.||220.127.116.11+||-||-||7||20 March 2017|
(*) Since version 2.11.0,
org.apache.sling.models.impl version 1.4.12 or higher is required (due to SLING-8781). This will be provided for AEM 6.4 and 6.5 in a future Service Pack. Until then, the Sling Models bundle is included in the
As with AEM, Adobe recommends that developers use the latest release and versions of the Core Components available that is compatible with the version of AEM that they are running in order to benefit from the most up-to-date fixes and features.
The following table details which versions of which components are contained in which releases of the Core Components.
|Release 1.0.0 - 1.0.6||Release 1.1.0||Release 2.0.0 - 2.0.8||Release 2.1.0||Release 2.2.0-2.2.0||Release 2.3.0-2.3.2||Release 2.4.0||Release 2.5.0||Release 2.6.0||Release 2.7.0-2.8.0||Release 2.9.0+|
|Page||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Title||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Image||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|List||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Breadcrumb||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Social Media Sharing||v1||v1||v1||v1||v1||v1||v1||v1||v1||v1||v1|
|Form Container||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Form Text||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Form Options||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Form Hidden||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Form Button||v1||v1||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2||v1, v2|
|Content Fragment||Sandbox||v1||v1||v1||v1||v1||v1||v1||v1, v2||v1, v2|
|Content Fragment List||v1||v1||v1||v1||v1|
Core Components are distributed via GitHub. This allows Adobe to more quickly add functionality to the components and also allow for community input outside of the AEM release cycle.
The Core Components are made available with defined AEM versions with which they are compatible. This means that one AEM version may support multiple versions or releases of the Core Components. This gives more flexibility than the former Foundation Components, which were tied to a specific version of AEM.
The major iteration of the Core Components are the versions. Each component has a version. Versions are denoted with v appended with a nonzero, positive integer such as v1 and v2. Versions are incremented only for changes that are not backward-compatible, which is normally the case for the introduction of new features and functionality.
Developers and administrators can recognize versions of the core components by a number in their resource type paths, and in the fully qualified Java class names of their implementations. This version number represents a major version as defined by semantic versioning guidelines.
For more details about core component versions, see the developer documentation of the Core Components.
The core components are made available through releases and represent the actual published artifacts available on GitHub. Releases are denoted with a decimal number of the format X.Y.Z and collect all core components together as a deliverable package.
Releases can contain multiple versions of the same component.
The same version of a component can appear in multiple releases.
Core Components are an integral part of AEM and supported as is, under the same terms and conditions as if they were delivered as part of the Quickstart.
Like other product features, the general rule of end-of-life is:
This gives customers at least one release cycle to move to the new version of the component, before support ends.
The version of each component clearly states the AEM versions that it supports. When support ceases for a version of AEM, then so does the support of the Core Components for that version of AEM.
For details about the support of component customizations, see the Customizing Core Components page of the relevant Core Components Version.
Adobe’s development emphasis has shifted to the Core Components and new features will continue to be added.
Nearly all Foundation Components have been deprecated with AEM 6.5 and only major bug fixes will be considered for the Foundation Components going forward.