Details
Description
I've been working with our Jakarta EE (EE4J) community to help debug this problem and the suggestion is to create an Issue against OSSRH to see if you can help.
The original problem was posted to our ee4j-build mailing list:
https://www.eclipse.org/lists/ee4j-build/msg00725.html
Some email assistance suggested this path:
"That feels right, the username is "jakartaee-platform-bot".
I think you need to create an issue on OSSRH and ask for a staging
profile to be created and the platform groupId "jakarta.platform" added
to it."
FYI, I also created an issue via Eclipse Bugzilla. They may be gone for the day, so I decided to go ahead with this OSSRH issue as well.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=550349
Populating this staging repository for our Jakarta EE 8 APIs is the last piece of our puzzle for releasing Jakarta EE 8. All of our other components are working just fine with deploying to maven. We're just not clear on what needs to be cleaned up for this final effort.
Let me know if you need any additional information. Or, if maybe this does belong in the Eclipse court and I'll update that bugzilla. Thanks!