Date: Fri, 29 Mar 2024 01:57:03 +0000 (UTC) Message-ID: <237183409.5.1711677423765@e5163ae9f391> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_696396348.1711677423765" ------=_Part_4_696396348.1711677423765 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
AEM 6.2 is released since April 2016.
This page lists information what to do to make your wcm.io-based Applica= tions compatible to AEM 6.2.
You should use the latest released bundles of all wcm.io Modules.
Especially you have to update the following bundles for compatibility wi= th AEM 6.2:
The main reason for this is that a lot of packages for the AEM API have = changed their major version number (although not changed much technically, = e.g. only because some deprecated features where removed).
There is a branch with a snapshot version of io.wcm.testing.a=
em-mock
2.0.0-SNAPSHOT compatible to AEM 6.2 and the latest Sling AP=
I changes and latest Oak version:
https://github.com/wcm-io/wcm-io-testing/tree/feature/aem62-api
The 2.0.0-SNAPSHOT version is also deployed to Sonatype OSS Snapshot Repository.
Because some major package version of the AEM 6.2 API changed you have t= o recompile your code against the latest AEM 6.2 API.
Alternatively you can compile against AEM 6.0 or 6.1 API (if you do not = need any of the new features in the API) and relax the import package versi= on ranges in your application bundle's POM files.
Example:
com.day.cq.commons
which was present as =
version 5.x in AEM 6.0 and 6.1, but has version 6.0 in AEM 6.2Update the maven-bundle-plugin
in your pom with a section l=
ike this:
<plug= in> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <configuration> <instructions> <Import-Package> com.day.cq.commons;version=3D"[5.7,7)", * </Import-Package> </instructions> <configuration> </plugin>