Integrate AWS SDK with AEM | Community
Skip to main content
varun249715
Adobe Employee
varun249715Adobe Employee
Adobe Employee
August 18, 2023
Solved

Integrate AWS SDK with AEM

  • August 18, 2023
  • 2 replies
  • 1594 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Mahedi_Sabuj

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-bundles-in-aem/m-p/611006 

2 replies

Mahedi_Sabuj
Community Advisor
Mahedi_SabujCommunity AdvisorAccepted solution
Community Advisor
August 18, 2023

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-bundles-in-aem/m-p/611006 

Mahedi Sabuj
    AMANATH_ULLAH
    Community Advisor
    AMANATH_ULLAHCommunity Advisor
    Community Advisor
    August 19, 2023

    @varun249715 

    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

    Amanath Ullah
      Terms & ConditionsAccessibility statement

      Loading footer...