Expand my Community achievements bar.

SOLVED

Failure in Exporting packages in start level in OSGI Bundle During Latest Version SDK Deployment in in Adobe cloud Manger pipeline

Avatar

Level 1
Hi,
I am encontering the error:[api-regions-exportsimports] Bundle aem -xxx--project.core:x.1.0 is importing package(s) [Package com.google.gson;version=[2.9,3), Package com.day.cq.commons.mail;version=[5.8,6), Package com.google.gson.annotations;version=[2.9,3)] in start level 20 but no visible bundle is exporting these for that start level in the required version range. 
While deployment of new Sdk version 2024.8.17569.20240822T203847Z-240700 in the cloud.
But it was sucessfull in local environment.
Eventhough,I have updated the aem analyser it doesn't have any effect do i need to change the Bundle version or is there any way possible to solve this problem.
 
please provide me documentation or any soluion.
 
Thanks
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Few points to cross check :
Check SDK version dependency in your project. Best to keep it same as that of your target deployment instance.
You will have to cross check the dependencies which you have added in your project for the problematic packages. For that, you can go to depfinder (/system/console/depfinder) and check for the packages for which you are getting the error. For e.g com.google.gson.annotations 
It will give you exact maven dependency which you can add in your project. 
It is possible that you are trying to use different version than the ones AEM provides OOB.
If you really want to use some other version then the one which AEM provides in that case, you will have to embed it in your project using filevault maven plugin. 
Hope this helps.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Few points to cross check :
Check SDK version dependency in your project. Best to keep it same as that of your target deployment instance.
You will have to cross check the dependencies which you have added in your project for the problematic packages. For that, you can go to depfinder (/system/console/depfinder) and check for the packages for which you are getting the error. For e.g com.google.gson.annotations 
It will give you exact maven dependency which you can add in your project. 
It is possible that you are trying to use different version than the ones AEM provides OOB.
If you really want to use some other version then the one which AEM provides in that case, you will have to embed it in your project using filevault maven plugin. 
Hope this helps.

Avatar

Level 1

 Thanks @h_kataria  it is successfully working if same sdk version is used in our pom