Overview
Currently (February 2016) AEM 6.2 is in beta phasereleased since April 2016.
This page lists information what to do to make your wcm.io-based Applications compatible to AEM 6.2.
Required
...
In AEM 6.2 load 17c there is a bug in the included Sling bundle org.apache.sling.jcr.base version 2.3.0 which prevents the wcm.io WCM Parsys bundle to work correctly - the "wcmio" namespaces is not registered correctly. This is fixed via SLING-5531 in version 2.3.2 of the bundle which should be available in AEM 6.2 load 18 or 19.
...
wcm.io
...
bundle
...
- Download from maven central: http://repo1.maven.org/maven2/org/apache/sling/org.apache.sling.jcr.base/2.3.2/org.apache.sling.jcr.base-2.3.2.jar
- Or from here when no yet available on Maven Central
...
versions
You should use the latest released bundles of all wcm.io Modules.
Additionally Especially you need the following bundle updates (currently only available as Snapshot in Sonatype OSS Snapshot Repository)have to update the following bundles for compatibility with AEM 6.2:
- io.wcm.wcm.commons 0.6.1-SNAPSHOT2
- io.wcm.config.api 0.5.5-SNAPSHOT6
- io.wcm.config.editor 0.6.3-SNAPSHOT4
- io.wcm.handler.url 0.78.1-SNAPSHOT0
- io.wcm.handler.media 0.10.1-SNAPSHOT2
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).
AEM Mocks for AEM 6.2
There is a branch with a snapshot version of io.wcm.testing.aem-mock 2.0.0-SNAPSHOT compatible to AEM 6.2 and the latest Sling API changes and latest Oak version:
https://github.com/wcm-io/wcm-io-testing/tree/feature/aem-6.2aem62-api
The 2.0.0-SNAPSHOT version is also deployed to Sonatype OSS Snapshot Repository.
Make your application compatible with AEM 6.2 API
Because some major package version of the AEM 6.2 API changed you have to recompile your code against the latest AEM 6.2 API.
...