Nor­mal­ly when a new ver­sion of CQ/AEM is released then you always have to go through the process around what Maven depen­den­cies you have to upgrade etc.

With AEM6.x this has become a lot sim­pler!

Now with AEM6 there is just one big Maven depen­den­cy that you need to add to your project, and you are good to go!

AEM6.0

<depen­den­cy>
   <groupId>com.adobe.aem</groupId>
   <arti­fac­tId>aem-api</arti­fac­tId>
   <ver­sion>6.0.0.1</ver­sion>
   <scope>pro­vid­ed</scope>
</depen­den­cy>

AEM6.1

<depen­den­cy>
   <groupId>com.adobe.aem</groupId>
   <arti­fac­tId>uber-jar</arti­fac­tId>
   <ver­sion>6.1.0</ver­sion>
   <scope>pro­vid­ed</scope>
   <clas­si­fi­er>obfuscated-apis</clas­si­fi­er>
</depen­den­cy>

AEM6.2+

<depen­den­cy>
   <groupId>com.adobe.aem</groupId>
   <arti­fac­tId>uber-jar</arti­fac­tId>
   <ver­sion>6.2.0</ver­sion>
   <scope>pro­vid­ed</scope>
   <clas­si­fi­er>apis</clas­si­fi­er>
</depen­den­cy>

From AEM6.2 the “apis” are pub­licly avail­able on https://​repo​.adobe​.com, for pre­vi­ous ver­sions you can down­load the unob­fus­cat­ed from the sup­port-por­tal: https://​day​care​.day​.com/​h​o​m​e​/​p​r​o​d​u​c​t​s​/​u​b​e​r​j​a​r​.​h​tml

NOTE: Make sure you put this depen­den­cy at the *end* of your depen­den­cy-list, this way if oth­er depen­den­cies con­tain new­er ver­sions they take prece­dence.

There is also doc­u­men­ta­tion that explains the uber­jar fur­ther: https://docs.adobe.com/docs/en/aem/6–2/develop/dev-tools/ht-projects-maven.html

Enjoy!

2 comments
senandung
senandung

thank you for describing this.