Skip to main content
dhanasekaranj70
Dec 27, 2016 7:45 AM UTC
Solved

com.day.cq.replication cannot be resolved

Hi All,

I am getting the following error when i deploy the 5.6.1 maven code to 6.2 instance. The build was successful but the bundles were not active. Bundle had the error "com.day.cq.replication,version=[5.12,6) -- Cannot be resolved"

When i checked the logs, i also found the below error.

osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.replication)(version>=5.5.0)(!(version>=6.0.0)))]

I tried to update the dependency of com.adobe.granite.replication.core from 5.12.2 to 6.0.14.

<dependency>
                <groupId>com.adobe.granite</groupId>
                <artifactId>com.adobe.granite.replication.core</artifactId>
                <version>6.0.14</version>
                <scope>provided</scope>
</dependency>

I am now getting Build failure error,

[ERROR] Could not resolve dependencies for project xyz.commons:bundle:1.0-SNAP

SHOT: Failed to collect dependencies at com.adobe.granite:com.adobe.granite.replication.core:jar:6.0.14: Failed to read artifact descriptor for com.adobe.granite:com.adobe.granite.
replication.core:jar:6.0.14: Could not transfer artifact com.adobe.granite:com.adobe.granite.replication.core:pom:6.0.14 from/to xyz-nexus (http://10.209.48.140:9099/nexus-2.3.1
/content/repositories/adobe-releases/): Connect to 10.209.48.140:9099 [/10.209.48.140] failed: Connection refused

Kindly suggest on solution to resolve this error.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Runal_Trivedi
Runal_TrivediAccepted solution
Level 6
Jan 3, 2017 10:54 PM UTC

Starting version 6.x, Adobe proposed using Uber Jar to consume any publicly available API of AEM and few other third party APIs. This is the reason your build is failing when you updated the version to 6.0.14, because this version itself is not exposed in Adobe's public repo - https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/com.adobe.granite.replication.core/

So certainly Uber Jar is the way to go. More details around Uber Jar can be found at:

https://docs.adobe.com/docs/en/aem/6-2/develop/dev-tools/ht-projects-maven.html

https://github.com/justinedelson/aem-uberjar-demo

Above link will help you understand how UberJar can be leveraged in a project.

and Jar is located here in Adobe's public Repo - https://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/uber-jar/6.2.0/

- Runal

View in thread

3 replies

JK_Kendall
JK_Kendall
Level 9
Jan 3, 2017 8:35 PM UTC

Hi,

I'm moving this post to the main AEM topic.

For reference, see How to Build AEM Projects using Apache Maven

My initial reaction, though, is to wonder why you would be deploy 5.6.1 Maven code to 6.2.  That would seem to be your problem right there.

- JK

Translate
Runal_Trivedi
Runal_TrivediAccepted solution
Level 6
Jan 3, 2017 10:54 PM UTC

Starting version 6.x, Adobe proposed using Uber Jar to consume any publicly available API of AEM and few other third party APIs. This is the reason your build is failing when you updated the version to 6.0.14, because this version itself is not exposed in Adobe's public repo - https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/com.adobe.granite.replication.core/

So certainly Uber Jar is the way to go. More details around Uber Jar can be found at:

https://docs.adobe.com/docs/en/aem/6-2/develop/dev-tools/ht-projects-maven.html

https://github.com/justinedelson/aem-uberjar-demo

Above link will help you understand how UberJar can be leveraged in a project.

and Jar is located here in Adobe's public Repo - https://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/uber-jar/6.2.0/

- Runal

Translate
smacdonald2008
smacdonald2008
Level 10
Jan 4, 2017 12:52 AM UTC

For step by step details on using Urber JAR in an AEM 6.2 project -- see: 

https://helpx.adobe.com/experience-manager/using/first-arch10.html

Translate
Terms & ConditionsAccessibility statement

Loading footer...