AEM 6.4 CQ Commons

[Shakthi1]

The below error is displayed when bundles are deployed in AEM 6.4.Request you to please advsie the exact versions of the Dependencies that should be inlcuded in POM file.

com.day.cq.commons,version=[5.6,6) -- Cannot be resolved

com.day.cq.commons.jcr,version=[5.6,6) -- Cannot be resolved

com.day.cq.mailer,version=[5.6,6) -- Cannot be resolved

com.day.cq.replication,version=[5.12,6) -- Cannot be resolved

Current versions are :

<dependency>

<groupId>com.day.cq</groupId>

<artifactId>cq-mailer</artifactId>

<version>5.6.4</version>

<scope>provided</scope>

</dependency>

<dependency>

<groupId>com.day.cq</groupId>

<artifactId>cq-commons</artifactId>

<version>5.6.4</version>

<scope>provided</scope>

</dependency>

<dependency>

<groupId>com.day.cq.wcm</groupId>

<artifactId>cq-wcm-commons</artifactId>

<version>5.8.8</version>

<scope>provided</scope>

</dependency>

<dependency>

<groupId>com.day.cq.wcm</groupId>

<artifactId>cq-wcm-core</artifactId>

<version>5.7.2</version>

<scope>provided</scope>

</dependency>

<dependency>

<groupId>com.day.cq.wcm</groupId>

<artifactId>cq-wcm-foundation</artifactId>

<version>5.6.4</version>

<scope>provided</scope>

</dependency>

The below was also included in the pom file.

<dependency>

<groupId>com.adobe.aem</groupId>

<artifactId>uber-jar</artifactId>

<version>6.4.0</version>

<classifier>apis</classifier>

<scope>provided</scope>

</dependency>

[Jörg_Hoh]

You should be able to remove the version numbers from explicit dependencies, as they are included in the uber.jar

Jörg

[Shakthi1]

Thanks a lot.I will remove those do build and deploy.

[Shakthi1]

I removed the version numbers .

like the below

<dependency>

<groupId>com.adobe.granite</groupId>

<artifactId>com.adobe.granite.replication.core</artifactId>

</dependency>

but get the below on the child pom xmls.

'dependencies.dependency.version' for com.adobe.granite:com.adobe.granite.replication.core:jar is missing.

[Jörg_Hoh]

Hm, my bad.

Then you need to add the version number of the bundle in your AEM 6.4 instance, you can find them in the OSGI webconsole (/system/console/bundles).

[Shakthi1]

Thanks for the clarification.

The below jars are not present in adobe repo.But these are the version on the AEM 6.4 bundle page.

Please can you advise the location where these jars can be obtained.

cq-msm-api-5.9.2.jar

cq-msm-core-5.11.24.jar

cq-commons-5.11.12.jar

cq-tagging-5.11.36.jar

cq-mailer-5.12.4.jar

Index of /repositories/public

[Shakthi1]

These jars are not present on ADOBE Repo. Please can you suggest some of the versions that will be compatible.

[arunpatidar]

Hi,

Remove all the dependencies for below from POM all the classes/packages are already part of uber jar.

cq-msm-api-5.9.2.jar

cq-msm-core-5.11.24.jar

cq-commons-5.11.12.jar

cq-tagging-5.11.36.jar

cq-mailer-5.12.4.jar

[Shakthi1]

Yes i deleted the references for the above jar .But now get the below

org.apache.sling.jcr.resource,version=[2.4,3) -- Cannot be resolved

This is the only issue now i ahve on the bundles.

Below is the code form the pom file.Can you suggest a version which i can add.

2.9.2 is not working.

<dependency>

<groupId>org.apache.sling</groupId>

<artifactId>org.apache.sling.jcr.resource</artifactId>

<version>2.9.2</version>

<scope>provided</scope>

</dependency>

[smacdonald2008]

You are trying to build a bundle the way they were built in AEM 5.x. That is - trying to reference separeate JAR files - that does not work now.

In AEM 6.4 - you build with Maven Archetype and reference the UBER JAR - as discussed here:

Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13

Building with the correct Maven Archetype automatically sets the correct dependencies.

[arunpatidar]

Hi,

this is also part of uber.jar

so you can remove this as well POM.

As Scott suggested build a fresh project using archetype 13 and compare your POM with that and remove unnecessary dependencies from your POM. If you are using eclipse you can see all the packages/Classes added inside uber jar.

[Shakthi1]

That means should I create the project structure from the beginning.

[smacdonald2008]

Its the best way for AEM 6.4 development. Trying to make a project built for an older AEM version work in the current version is error prone.

Much better to build an AEM project with its corresponding Maven Archetype project. For 6.4 - its Archetype 13.