Adobe Maven Repo: The specified blob does not exist

[lvalenti]

Hi, I'm trying to build an old AEM project on my PC and I have this error after "mvn clean install" command

$ mvn clean install -q
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:4.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.felix:maven-bundle-plugin:jar:4.1.0 @
[ERROR] Unknown packaging: bundle @ line 27, column 16
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project it.xxx.xx.xxxxxxxxxx:xxx.core:1.0-SNAPSHOT (C:\Users\xxxx\Development\aem-projects\xxxx\core\pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:4.1.0 or one of its dependencies could not be resolved: Failed to read
artifact descriptor for org.apache.felix:maven-bundle-plugin:jar:4.1.0: Could not transfer artifact org.apache.felix:maven-bundle-plugin:pom:4.1.0 from/to adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public transfer failed for https://repo.adobe.com/nexus/content/groups/public/org/apache/felix/maven-bundle-plugin/4.1.0/maven-...: Tag mismatch! -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 27, column 16
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException

If I open the link

https://repo.adobe.com/nexus/content/groups/public/org/apache/felix/maven-bundle-plugin/4.1.0/maven-...

in Chrome, I get the error:

<Error>
<Code>BlobNotFound</Code>
<Message>The specified blob does not exist. RequestId:c000c90c-001e-004f-5d5c-fece12000XXX Time:2022-11-22T10:22:58.1530119Z</Message>
</Error>

What's the problem?

[Avinash_Gupta_ · Accepted solution]

@lvalenti 

 repo.adobe.com has been decommissioned. You would have to remove it's dependency from maven-bundle-plugin:jar:4.1.0:

Make changes in your pom.xml to use Uber.jar. and compile code against this. The AEM Uber jar includes all AEM APIs as a single dependency in your Maven project’s pom.xml.

<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.9</version>
<scope>provided</scope>
</dependency>

[SantoshSai]

Hi @lvalenti,

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.

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

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

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.

When you said it's old project FYI:

Adobe repo url was made secured. from

http://repo.adobe.com/nexus/content/groups/public/ to https://repo.adobe.com/nexus/content/groups/public/ ("https" protocol instead of "http")

Instructions on how to use repo were displayed here https://repo.adobe.com/index.html

Also, have a look at: https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-17454.html?lang=en

Hope that helps!

Regards,

Santosh

[Avinash_Gupta_]

Secured URL of nexus repo is also not accessible https://repo.adobe.com/nexus/content/groups/public/ 

[SantoshSai]

Yes! you are right, hence specified as FYI.

[lvalenti]

Thank you all.

Actually, it was a problem in the antivirus policy of my organization and not a development configuration issue.