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!
Solved! Go to Solution.
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
Aaah, understood.
Been successful creating an HTL component that pulls data from the JCR using these APIs:
We will release this article next week.
This uses Maven Arch 13. UBER 6.4, a system user, Java code, and HTL.
i got the same issue while upgrading to 6.4.
is there a link to the above mentioned article.
Thanks!
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
atulj26424737 Thanks! It worked.!
Views
Likes
Replies