Hi,
we usually have used a "AEM 6.x parent pom" for our projects, which we have created manually. This AEM parent pom defined simply the correct versions of the needed depedencies for the specific AEM version. Currently the "uber-jar" approach is the way to manage these AEM dependencies as far as I have seen. But this approach actually breaks the idea of managing transparently the dependencies in your project. As a developer I would like to have the control over my dependencies during development and be sure to access the correct versions of some classes. The uber-jar is acutally thought to use it in runtime scenarios, where you want to deliver your application with all the needed dependencies included.
I would appreciate to have some official Adobe AEM 6.x parent poms, which we can reference from our projects.
What do you think about that and is there any such parent pom already available?
Views
Replies
Total Likes
Is actually the same question as here: forums.adobe.com/message/9573597
Views
Replies
Total Likes
You can also look at the Core Components as an example: GitHub - Adobe-Marketing-Cloud/aem-core-wcm-components: AEM Core WCM Components
Views
Replies
Total Likes
Thanks Feike Visser, but as I have seen so far they also use this uber-jar, see in the parent pom of the project.
Views
Replies
Total Likes