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
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Imported Packages Cannot be resolved

rk39193348
Level 4
Level 4

Hi All,

I am getting the above dependency issues in system console, but my build is successful in eclipse. I checked in http://localhost:4502/system/console/depfinder, but the dependency when added in eclipse gives me build issues. Do you know how to resolve this?  

 

com.day.cq.wcm.api,version=[1.27,2) -- Cannot be resolved
com.googlecode.htmlcompressor.compressor -- Cannot be resolved

org.apache.commons.lang,version=[2.6,3) -- Cannot be resolved

org.apache.sling.models.annotations,version=[1.5,2) -- Cannot be resolved
org.apache.sling.models.factory,version=[1.4,2) -- Cannot be resolved

org.json.simple,version=[1.1,2) -- Cannot be resolved
org.json.simple.parser,version=[1.1,2) -- Cannot be resolved
org.jsoup,version=[1.8,2) -- Cannot be resolved
org.jsoup.nodes,version=[1.8,2) -- Cannot be resolved
org.jsoup.select,version=[1.8,2) -- Cannot be resolved
org.osgi.service.component,version=[1.4,2) -- Cannot be resolved

 

Regards,

Ranjitha

 

1 Accepted Solution
Jörg_Hoh
Correct answer by
Employee
Employee

Most often that's caused by building against a version X of the uber.jar and deploying into a different version Y of AEM. Can you share which version of the uber.jar you are referencing in your POM and what AEM version you are deploying to?

 

Regards,

Jörg

View solution in original post

5 Replies
Albin_Issac
Community Advisor
Community Advisor

Are you importing all the required packages to the bundled?

 

Verify if you have some configuration like below in the core pom.xml

 

Import-Package: javax.annotation;version=0.0.0,*

 

Another issue might be due to the version mismatch, ensure the correct uber-jar version included in your parent pom.xml file.

 

Regards

Albin I

www.albinsblog.com

 

rk39193348
Level 4
Level 4
Still I am getting same issue, It is not getting resolved
Jörg_Hoh
Correct answer by
Employee
Employee

Most often that's caused by building against a version X of the uber.jar and deploying into a different version Y of AEM. Can you share which version of the uber.jar you are referencing in your POM and what AEM version you are deploying to?

 

Regards,

Jörg

View solution in original post

Jörg_Hoh
Employee
Employee
In that case this is totally expected behavior. Please synchronize the version of the uber.jar with the AEM version you are using.