AEM Project Maven dependency Jars

[varaande]

Hi Team

Currently we are working on Government Project where we are not allowed to used Public repositories . We need to all AEM and Forms related dependent jars to our Internal Repositories .

As per below link , Central repo having 26 and Adobe public having 19 dependency jars But usages only two in Central Repo and one Adobe public .

What is deference o Central repo vs adobe Public (Most of the time we used adobe public repo only ) , Do i need to take all the jars uploaded to our internal repo or latest sdk jar enough for AEM (ex: com.adobe.aem) & aem osgi forms(forms add-on) ex: com.adobe.aemfd) .

https://mvnrepository.com/artifact/com.adobe.aemfd/aemfd-client-sdk

Currently we added two jars related SDK(AEM as a cloud service) but we using AEM6.7.20 on-premises with adobe OSGi Forms add-on package (project completely OSGI forms) ,is there any risk use SDK jars for AEM6.5 on-premises Project for Local development 
SDK:

https://mvnrepository.com/artifact/com.adobe.aem/aem-sdk-api/2024.2.15262.20240224T002940Z-231200

AEM Osgi Forms:
https://mvnrepository.com/artifact/com.adobe.aemfd/aemfd-client-sdk/6.0.1192

[ankumitt · Accepted solution]

Hi @varaande ,

The difference between the Central and Adobe Public repositories is as follows:

• Central is mapped to: https://repo1.maven.org/maven2/
• Adobe Public is mapped to: https://repo.adobe.com/nexus/content/repositories/public/

Adobe Public was an old Nexus-based repository, and Central was simply mirroring it. However, Adobe Public is no longer used to push the aemfd-client-sdk artifact.

The latest versions of aemfd-client-sdk are now pushed directly to Central. Therefore, you only need to add artifacts from Central to your internal repository.

In general, pushing only the latest version of artifacts to your internal repo should suffice, especially if you are using the latest version of the product and do not specifically require any older versions.