Maven Deploy `at_client` to Nexus OSSRH: All jobs have failed

[cpswan]

Describe the bug

For the past couple of months the Maven Deploy workflow has been failing.

Steps to reproduce

1. First I review a Dependabot PR
2. Then I approve and merge to trunk
3. And then the Maven Deploy workflow is triggered and fails:

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17.461 s
[INFO] Finished at: 2025-08-13T07:55:44Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy (injected-nexus-deploy) on project at_client: Failed to deploy artifacts: Could not transfer artifact io.github.atsign-foundation:at_client:jar:sources:1.0-20250813.075527-164 from/to ossrh (https://s01.oss.sonatype.org/content/repositories/snapshots): status code: 403, reason phrase: Forbidden (403) -> [Help 1]
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/MojoExecutionException
Error: Process completed with exit code 1.

Expected behavior

Maven Deploy runs clean

[JeremyTubongbanua]

Start from scratch was our conclusion in arch

Investigate GItHub trusted publishing method , avoid having to wrangle secrets
Another potential barrier --> "to create a proper, we might have to pay? potential exception for Open Source Projects"

[JeremyTubongbanua]

• Get email, Get org.atsign namespace, then get a token
• Goal : publish what we have now, then start making changes, publishing new versions with proper versioning
• Use Central publishing maven plugin --> which has GPG signing

[akafredperry]

@cpswan please can you create an email maven@atsign.com which we can use to register a user at https://central.sonatype.com
once this is done will create an account and claim the org.atsign namespace

[cpswan]

@akafredperry email group is done. You should have a test email from my personal account.

[akafredperry]

I have registered the following user

• name : atsign
• email: maven@atsign.com
• password: I will share this separately

I have registered the following namespace

• org.atsign

The verification process which completes this registration requires the following...

To prove the ownership of this Namespace, a DNS TXT Record is required with the same value that matches its Verification Key(7olrha6gct).

For the Namespace org.atsign you will need to create TXT Record:

7olrha6gct

Domain Registrars services have different procedures for adding a TXT Record, please check your registers documentation to find out how to add a TXT Record.

@cpswan who has the power to create the required DNS record for the domain org.atsign

[JeremyTubongbanua]

thank you @akafredperry !