Hello all,
We are in the phase of migrating from AEM managed service to AEM cloud service, we want to deploy third-party jar. When we are in AEM managed services we have created an OSGI bundle from this jar but in AEM as a cloud, we can not upload and install this OSGI bundle using package manager because it will not allow installing immutable content manually.
Please suggest what's the process to be followed to deploy the jars which are not part of OSGI container.
Thanks,
Kishore
Solved! Go to Solution.
Views
Replies
Total Likes
you can put this osgi bundle in the resources folder in your project core and copy in apps.ui /apps/myapp/vendor/install using POM similar to core bundle
you can put this osgi bundle in the resources folder in your project core and copy in apps.ui /apps/myapp/vendor/install using POM similar to core bundle
Hi @arun , by resources folder you mean, core/src/test/resources or core/src/main/ (create a folder resources) here?
also, by same pom you mean to use the <embedded> under plugins?
Please help, thank you.
Regards,
Sravan
Hi @B_Sravan ,
Any Luck in resolving the above issue?
Have tried including our custom bundle under the .core/src/main/resources/xxxx.jar. As well having the embedded entry in all/pom.xml and dependency in main& core pom.xml.
There is always a warning and the jar is not pushed to our install.
[WARNING] No matching artifacts for Embedded:
@arunpatidar , @GK-007 & @B_Sravan - Please suggest if there is an resolution and steps to be followed.
Thanks
Cheers
Thabrez
Views
Replies
Total Likes
Please check
I have embedded a sdi jar in all packages and installing in aem with deployment.
Views
Replies
Total Likes
Thanks for the quick reply @arunpatidar .
And yes we were successful in getting the embedded jars , where artifactId repository is available ( like Jsoup, sling..etc).
We were looking more towards the custom Jar's, where (in-house/company) artifactId repository is not available.
As mentioned above in the chain, have tried placing our custom jar is resources path (<app_project>\core\src\main\resources) and as well tried the older way of placing in the install folder (<app_project>\ui.apps\src\main\content\jcr_root\apps\migration\install).
even tried the below approach in the link(https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/embedding-and-installing-e...), so no luck here too .
Seems like integrated/embedding the custom bundles/ jars is deprecated in AEMasCS, any guidance is much appreciated.
Cheers
Thabrez
Views
Replies
Total Likes
can you try adding jar/bundle directly inside
/apps/your-apps/install folder, just to check if it works or not?
Views
Replies
Total Likes
It is an old thread but here is an ExL tutorial on How to install 3rd party artifacts (bundle, Java & packages) that are not part of Maven Central.
https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/install-t...
Thanks for sharing @sachin-mali
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies