AEM 6.4 beta, Apache Sling JCR Resource Resolver not present | Community

Level 2

Solved

AEM 6.4 beta, Apache Sling JCR Resource Resolver not present

Forum|Forum|7 years ago
February 1, 2018
25 replies
16464 views

Hi all

I'm trying to migrate an app so it works on AEM 6.4 beta, but I ran into the following problem:
When I install my bundle. I get the following error:

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

Right now, I'm using version 2.9.2 of org.apache.sling.jcr.resource. Here's the pom dependency:

<dependency>

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

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

<version>2.9.2</version>

<scope>provided</scope>

</dependency>

I checked in AEM's web console, and searched for that dependency using the dependency finder ( http://localhost:4502/system/console/depfinder ), and It turns out that package "org.apache.sling.jcr.resource" cannot be found in AEM 6.4 beta:

I checked in AEM 6.3, but I do get a result there:

It is because of this that I suspect that the problem is that this dependency is not present in AEM 6.4 beta. But still, I'm not an expert on dependencies so I'm not sure if this is the case, or if it's a problem on my project.

I'd appreciate if someone can point me in the right direction on this. Basically I want to check if the problem is related to AEM 6.4 beta dependencies.

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Altham

Hi,

Actually these issues are due to changes in uber jar file i.e. interfaces and classes has been restructured in uber jar 6.4.

You can decompile uber jar and see the changes by yourself.

Taking an example of org.apache.sling.jcr.resource ....

org.apache.sling.jcr.resource.JcrResourceUtil is changed to com.day.cq.commons.jcr.JcrUtil

org.apache.sling.jcr.resource.JcrResourceConstants changed to org.apache.sling.jcr.resource.api.JcrResourceConstants

Links to figure out deprecated API's

https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/deprecated-list.html

https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/reference-materials/javadoc/deprecated-list.html

Community Advisor

Community Advisor

For me I am not able to login to the server itself after load18 . It is not taking admin/admin as credentials

Level 10

AFAIK, there is no issue with login for load18

Though you might be hitting AEM 6.4 beta, default login is not working

Make sure you do not have any space in path to jar file else it will through an crypto exception in stderr.log

References from Windows OS

Path with spaces - C:\AEM Stuff\aem 6.4 - will not work

Path without spaces - C:\sample\aem64 - will work

Community Advisor

Community Advisor

Still not working login_error

Level 10

is this the fresh instance of load18?

Community Advisor

Community Advisor

yup. Just now downloaded a new build from beta site.

Community Advisor

Community Advisor

Thanks Praveen. This got resolved by renaming the folder to all small.

Community Advisor

Community Advisor

I just ran the 6.4 and checked your issue. For me evrything looks fine. and the bundle you referred is also present

Can you take a fresh jar download from Adobe Prerelease

ralvarado88Author

Level 2

Thanks! Yes, apparently it was an issue with my jar. Thanks for your help!

Community Manager

Community Manager

It is against NDA to post AEM 6.4 beta questions on the main forums. You should be asking these in the Beta forums (Adobe prerelease) set for it.

-Kautuk

Kautuk Sahni

Level 2

having the same issue with recently release AEM 6.4

Show more replies