[RelEng] Migrate Maven publication to new Central Portal API

[HannesWell]

This is currently a draft as the tokens are not yet available for all three namespaces (platform, jdt and pde).

[HannesWell]

@merks FYI this pipeline passed one first run, but only for the platform namespace (for the other two namespaces the tokens are missing).

@elsazac can you please check the new Central Portal if there has been an deployment for the o.e.platform namespace and check if it's correct and discard it so that it is ** !NOT! RELEASED**!
With the old OSSRH it was the Drop button as you described in #2730 (comment), but I don't know how this works with the new Portal. If you are in doubt, please just do nothing and let's conduct some research. Or maybe Ed can tell from his experience with EMF?
Thanks in advance.

[elsazac]

@HannesWell ,

I was checking through the portal and under namespaces this is what I see : (all of them ie JDT, PDE and Platform can be seen under available namespaces)

.
.
.
.
Meanwhile under deployments there aren't any repositories

Actually, I don’t see anything under the Deployments tab — which might mean the repositories haven’t yet reached the staging phase for deployment. I’m not entirely sure though, as I’m still getting familiar with this myself.

[elsazac]

But there’s also an option to publish components by selecting files from the local file system in the OS.

[merks]

@HannesWell

Are we sure (or expecting) that the problem of only being able to see a deployment made with one's own ID has been addressed already?

[elsazac]

And then just this also in my notifications tab, This is regarding the platform namespace; Is this what you were looking for ?? apart from that there aren't much options available too.

[HannesWell]

Thank you @elsazac for checking and providing all these information. That makes me confident that the deployment actually worked.

Are we sure (or expecting) that the problem of only being able to see a deployment made with one's own ID has been addressed already?

Good point, that's probably the reasons why Elsa cannot see the full deployment.

In the meantime, I'll just continue to use the Publisher API to manage (inspect and drop) the deployment:

• https://central.sonatype.org/publish/publish-portal-api/#verify-status-of-the-deployment

In general we could also built that into a Jenkins job, but that would mean that any Committer can publish a release (which is technically already the case today, but one has to know about the mentioned API and how to use it).

[HannesWell]

This is now fully functional and ready for review. According to my testing it works as desired.
I extended it to also await the verification of the deployment to the central portal and to store the deployment's id.

Later we could use that to automate the final publication step and perform it in the Make visible job (that I would like to rename to Publish Release). Buts something else.

[HannesWell]

This now ready for submission and with this we can consider the migration to the new Maven Central Portal as completed.

Later we could use that to automate the final publication step and perform it in the Make visible job (that I would like to rename to Publish Release). Buts something else.

I'll create a follow-up PR to work out this proposal and describe the further integration I have in mind for the Maven publication.