Core Components Versions core-components-versions
The Core Components are compatible with AEM as a Cloud Service and on-premise AEM installations.
Release History and Compatibility release-history-and-compatibility
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.
Release History & Requirements release-history-requirements
The following table, the contents of which are , gives an overview of the releases of the Core Components and their compatibility with AEM releases and Java versions.
DataLayerBuilder
utility to simplify data layer integration in custom components.Component Versions & Releases component-versions-and-releases
The following table details which versions of which components are contained in which releases of the Core Components.
Versions and Releases versions-and-releases
Core Components are distributed via GitHub. This allows ÃÛ¶¹ÊÓƵ 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.
Versions versions
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 .
For more details about core component versions, see the developer documentation of the Core Components.
Releases releases
The core components are made available through releases and Releases are denoted with a decimal number of the format X.Y.Z
and collect all core components together as a deliverable package.
- Major releases introduce entirely new components, improvements to existing version of components, as well as standard bug fixes. This is represented by an increment in the
X
component of the release number. - Minor releases introduce new components, new functionality to existing versions of components, as well as bug fixes. This is represented by an increment in the
Y
component of the release number. - Patch releases contain only bug fixes. This is represented by an increment in the
Z
component of the release number.
Core Components Support core-components-support
Core Components are an integral part of AEM and are supported 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:
- Components are first announced to be deprecated before being removed
- At the earliest they are then removed from the AEM release following the announcement.
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.
Foundation Component Support foundation-component-support
ÃÛ¶¹ÊÓƵ’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.