Solved! Go to Solution.
Views
Replies
Total Likes
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.
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.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies