Hi All,
I am facing an issue with integrating AWS Sdk with AEM. After deploying code to local some of the dependencies are not getting resolved.
I am using AEM CS where bnd-mvn-plugin is used. I am looking for a way where I can ignore some of the transitive dependencies to be a part of OSGI bundle.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @varun249715,
In the majority of instances involving third-party bundles, the resolution of the Maven dependency in both the main pom.xml and the core pom.xml results in the successful inclusion of the required bundle.
Nevertheless, there are situations where this automatic process does not occur as expected. In such scenarios, it becomes necessary to prepare the dependency for OSGi compatibility and then embed it into the system.
To accomplish this, you can refer to the instructions provided in the documentation.
https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html
For detailed changes and procedures, you can refer to this GitHub commit: https://github.com/Sady-Rifat/aem-demo/commit/65f8ce112744134728bf2f85d7bc5f131a2ef290
Same problem is being discussed here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-third-party-bund...
Hi @varun249715,
In the majority of instances involving third-party bundles, the resolution of the Maven dependency in both the main pom.xml and the core pom.xml results in the successful inclusion of the required bundle.
Nevertheless, there are situations where this automatic process does not occur as expected. In such scenarios, it becomes necessary to prepare the dependency for OSGi compatibility and then embed it into the system.
To accomplish this, you can refer to the instructions provided in the documentation.
https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html
For detailed changes and procedures, you can refer to this GitHub commit: https://github.com/Sady-Rifat/aem-demo/commit/65f8ce112744134728bf2f85d7bc5f131a2ef290
Same problem is being discussed here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-third-party-bund...
Try creating new module similar to core and include dependencies in it.
Here we need to create an OSGi bundle out of third party non-osgi dependency using maven-bundle-plugin
Below article mentions all the steps for it
https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html
Views
Likes
Replies