Highlighted

How to add a third party bundle to you AEM package ?

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

23-02-2018

I had this question for a long time , especially for Maven bundles. I am not sure if this is the right way but I figured out something after going through many (actually not dat many ) How to add a third party bundle to you AEM package ? | LinkedIn  Hope this helps .

I would really like to know if this is a right way to do this. Anybody who has previously done this can let me know if this is ok. For me the packages are behaving as expected even when I do fresh build.

Replies

Highlighted

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

25-02-2018

I have updated this . Thanks to Jörg Hoh and bsloki​ for pointing to the right method

Highlighted

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

26-03-2018

Jörg Hoh I tested this in 6.2 . Embed for particular jars is working only in 6.3 and above.

Highlighted

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K
Jörg_Hoh
Employee

27-03-2018

The content-package-maven-plugin is independent from AEM versions. I use this approach since at least AEM 5.6 times...

Based on my experience I cannot confirm that this is something solely for 6.3 and later. Maybe you can be more specific here.

regards,

Jörg

Highlighted

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

27-03-2018

Hi Jorg

   I am trying to add some AWS jars to the package . It works fine in 6.3 for me . But the same thing when I tried for my existing project which is in 6.2 , even thought I can see the bundle under install folder, it is not showing up in the felix console.

1452057_pastedImage_2.png

1452058_pastedImage_3.png

I am embedding the above bundles to my package. This works fine in 6.3 , but the AWS bundle is not getting installed in the felix console. It is reflecting in the install folder of my project but not getting installed in the felix console . I get the below error in the console in 6.2 . Clearly my bundle is not able to resolve this dependencies. So I assume this shud be an issue only with the AWS bundle alone.

Highlighted

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K
Jörg_Hoh
Employee

29-03-2018

I guess that's rather a dependency problem on AEM 6.2 on an OSGI level. But nevertheless the way how to bring these bundles into an AEM instance (even if the bundle is not properly resolving then) is agnostic to the AEM version.

Jörg

Highlighted

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

29-03-2018

Gotcha !!