Overview
Currently (February 2016) AEM 6.2 is in beta phase.
This page lists information what to do to make your wcm.io-based Applications compatible to AEM 6.2.
Required wcm.io bundle versions
You should use the latest released bundles of all wcm.io Modules.
Additionally you need the following bundle updates (currently only available as Snapshot in Sonatype OSS Snapshot Repository):
- io.wcm.wcm.commons 0.6.1-SNAPSHOT
- io.wcm.config.api 0.5.5-SNAPSHOT
- io.wcm.config.editor 0.6.3-SNAPSHOT
- io.wcm.handler.url 0.7.1-SNAPSHOT
- io.wcm.handler.media 0.10.1-SNAPSHOT
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).
Required Sling Bundle Updates
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.
Until then you have to apply this workaround before installing your wcm.io-based application:
- Upload the Version 2.3.2 of the bundle via Felix Console and start it
- 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
- Restart the AEM 6.2 instance
- Deploy the wcm.io-based application including the wcm.io Bundles