AEM 6.2

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 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:

1. 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
2. Restart the AEM 6.2 instance
3. Deploy the wcm.io-based application including the wcm.io Bundles

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).

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.

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 version ranges in your application bundle's POM files.

Example:

• Your application uses a class from the package 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.2

• Update the maven-bundle-plugin in your pom with a section like this:

  <plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <configuration>
      <instructions>
        <Import-Package>
          com.day.cq.commons;version="[5.7,7)",
          *
        </Import-Package>
      </instructions>
    <configuration>
  </plugin>