Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

com.day.cq.wcm.api cannot be resolved

Avatar

Level 2

Hi All,

     Can any one provide me solution to resolve the following :      

  • com.day.cq.wcm.api,version=[1.29,2) -- Cannot be resolved
  • org.apache.sling.api.resource,version=[2.12,3) -- Cannot be resolved

Here I am using AEM 6.5 still I am using the latest Uberjar eventhen I am getting this issue 

Thanks,

Pavan

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Adobe_CQ_Dispat,

Can you let know if AEM 6.5 is a fresh install type or in-place upgraded instance?

Cross check

  • The below OOB bundles (which are not resolved - WCM and Sling resource API)and look for the version it is exporting and check it is active
  • Uber jar entry is in par with the AEM instance version

 If everything looks fine and still an issue, try to restart the framework if it is your local or any lower environments - http://localhost:4502/system/console/vmstat

View solution in original post

8 Replies

Avatar

Community Advisor

Is this issue happening in your local environment ?

Do you see any error in logs?, can you provide error log trace.

Avatar

Correct answer by
Community Advisor

Hi @Adobe_CQ_Dispat,

Can you let know if AEM 6.5 is a fresh install type or in-place upgraded instance?

Cross check

  • The below OOB bundles (which are not resolved - WCM and Sling resource API)and look for the version it is exporting and check it is active
  • Uber jar entry is in par with the AEM instance version

 If everything looks fine and still an issue, try to restart the framework if it is your local or any lower environments - http://localhost:4502/system/console/vmstat

Avatar

Level 2
Can you tell how to check uber jar version in aem 6.5. I checked root pom.xml and could not find dependency for it

Avatar

Community Advisor

Hi @Shivam_S,

If you have created project using AEM Maven Archetype, you would have this dependency entry available by default in main pom.xml and in core/pom.xml (with just the groupId and artifactId entry)

<dependency>
 <groupId>com.adobe.aem</groupId>
 <artifactId>uber-jar</artifactId>
 <version>6.5.0</version>
 <classifier>apis</classifier>
 <scope>provided</scope>
</dependency>

 

Avatar

Level 2
I followed wknd tutorial and created project using archetype given in project setup page. i checked both main pom.xml and core/pom.xml but there is no uber jar dependency present

Avatar

Community Advisor

@Shivam_S,

Use this WKND project code base from this GitHub location - https://github.com/adobe/aem-guides-wknd

If you could see here <uber.jar.version> is available as properties in main/pom.xml - You can specify the desired AEM version. 

The same is used in core/pom.xml for the artifactId, uber-jar

Avatar

Employee

* Is your uber jar version compatible with the exact version of your AEM 6.5 that you are using?

Example:

AEM: 6.x.y

Uber Jar: uber-jar-6.x.y-apis.jar

or

uber-jar-6.x.y-apis-with-deprecations.jar

 

Found another community article that might be helpful:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-day-cq-dam-core-cannot...