Not able to access repo.adobe.com

[fanindras]

Hello Team,

We are not able to access repo.adobe.com, Any Maintenance issue? We are unable to build AEM projects across the globe. Please help.

@kautuk_sahni @Singh_Jagpreet 

[fanindras]

16:26:04 [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in central

[fanindras]

Adding content-package-maven-plugin resolution error for reference: 16:26:04 [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in central

[#4 · Accepted solution]

The decommissioning of repo.adobe.com has been postponed, as a few artifacts have not been properly migrated. You should be able to use it again.

[Shashi_Mulugu]

Always keep an eye on: https://status.adobe.com/products/1175/en

I can see this up: https://repo1.maven.org/maven2/com/adobe/cq/

//From AEM 6.4.8.2 onwards, UberJar and other related artifacts are available in the Maven Central repository instead of the Adobe Public Maven repository (repo.adobe.com). The main UberJar file is renamed to uber-jar-<version>.jar . As a result, there is no classifier , with apis as the value, for the dependency tag.

See: https://docs.adobe.com/content/help/en/experience-manager-65/developing/devtools/ht-projects-maven.h...

Adobe Public Maven Repository

NOTICE: THIS REPOSITORY HAS BEEN DECOMMISSIONED

All artifacts have been moved to Maven Central. Please REMOVE repo.adobe.com from your maven settings. This server will be shut down soon.

[Shashi_Mulugu]

Thank you but if you take "content-package-maven-plugin" in latest archetype is 1.0.2 but in maven central 0.5.24 is the latest, so builds are failing. please help.

[Shashi_Mulugu]

@kautuk_sahni