Can this plugin be used as a replacement of official sonatype `central-publishing-maven-plugin` ?

[sbernard31]

There are concerns about official Sonatype central-publishing-maven-plugin.

This plugin is not developed transparently as a good open source project should be .. There is no code repository and no bug tracker... only possible support by email...

And when I contact them, I get a surprising answer :

As of now, we don't plan to open source the maven plugin since it contains proprietary code from Sonatype

Fun fact, in maven central the project is claimed to be licensed under The Apache License, Version 2.0...

(More details about that concerns at here)

So :

• Sonatype choice doesn't inspire trust...
• A central-publishing-maven-plugin fork exists but what will happen to it if sonatype claim its plugin is not open source. And also it is maintained by an unknown organization (at least to me).

Finally a real open source alternative maintained by a well-known and trusted foundation like this one would be a great addition to java ecosystem.

But is this plugin can be used as a replacement to publish to Maven Central ?

I mean this plugins seems to be able to do a lot.
But is there a simple way to do what is achieved with current sonatype plugin usage ?
I guess answer is here but not clear to me what is the recommended simple approach for someone which just need to migrate from central-publishing-maven-plugin to this plugin ? 🤔

[sbernard31]

Not directly linked to the question

But sonatype answer me again by mail and this time I get another response :

Hi , we had a bit of miscommunication in the recent handovers. I do intend to open source the plugin and the validations that are run so that the community can adapt them to their own tools as needed, and eventually to contribute enhancements and tweaks to the validations. As noted in the original reply, the validations are still intertwined with some internal Nexus code (because that's where they started, as part of early Nexus Pro features) and this is why it hasn't been opened up yet. The immediate focus of the team is still on some operational enhancements for publishing throughput and then self service organization management which represents the bulk of our current support tickets. After that, I'm expecting we'll be able to get this sorted out.

....
--Brian

(kind of confusing to me)