Platform and RelEng JIPP misses authorization for eclipse-maven2 repo

Summary

From the platform JIPP we can't deploy artifacts to the eclipse-maven2-snapshots repo any more since the migration to Nexus3.

Could it be that the platform JIPP is not authorised any more for the eclipse repos? Deploying to eclipse repos from the releng JIPP works for some time now but also failed immediately after the migration with a similar message. I assume that was fixed by the IT team too, but I can't find a corresponding gitlab issue.

Identified in the context of

• https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/pull/3719

Relevant logs and/or screenshots

https://ci.eclipse.org/platform/job/eclipse.platform.releng.aggregator/job/master/4256/console

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy (default-deploy)
 on project eclipse-platform-parent: Failed to deploy artifacts: Could not transfer artifact
 org.eclipse:eclipse-platform-parent:pom:4.40.0-20260319.055702-35 from/to repo.eclipse.org
 (https://repo.eclipse.org/content/repositories/eclipse-snapshots/):
 status code: 401, reason phrase: Unauthorized (401) -> [Help 1]

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Can't deploy updates of the parent pom.xml and sdk-target for use in all TLP submodules.