This conversation has been locked due to inactivity. Please create a new post.
This conversation has been locked due to inactivity. Please create a new post.
I have seen somewhere in the forum people recommend to use the maven scope system. if I include my jar location(local maven repo path) in the system path and embed that in the pom, the jar will be embedded in the AEM bundle and it would work fine. If I commit that code in the GIT other developers will need to change the repo path location corresponding to the local. Is that a good approach? Or do we have a recommended practice for this?
Solved! Go to Solution.
Views
Replies
Total Likes
Sharing a blog which explains how to use Third-party bundles when:
https://techrevel.blog/2023/09/27/managing-third-party-dependencies-in-aem/
It also covers the configs needed for deployment via Cloud manager
If you commit a JAR into GIT, then when other ppl clone that repo, and want to build the OSGi bundle, you are correct - they must make sure the Maven can find that JAR during the build process.
Danial covers use of GIT in the project setup section here -- Getting Started with AEM Sites Chapter 1 - Project Setup
Views
Replies
Total Likes
If you look at the SOLR Article - you can see how POM is configured to pickup the required dependencies - Adobe Experience Manager Help | Integrating SOLR with Adobe Experience Manager 6.4
Views
Replies
Total Likes
Sharing a blog which explains how to use Third-party bundles when:
https://techrevel.blog/2023/09/27/managing-third-party-dependencies-in-aem/
It also covers the configs needed for deployment via Cloud manager
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies