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