Skip to content

Migrate from OSSHR (which reach End of Life) to Maven Central for master#1735

Merged
sbernard31 merged 2 commits intomasterfrom
maven_central2
Nov 19, 2025
Merged

Migrate from OSSHR (which reach End of Life) to Maven Central for master#1735
sbernard31 merged 2 commits intomasterfrom
maven_central2

Conversation

@sbernard31
Copy link
Copy Markdown
Contributor

All is in the title more.

We face an issue about not deploying leshan-integration-test which lead us to create a dedicated parent POM for module to publish. (and so not use it with leshan-integration-test.
This is ok for master (Leshan v2.x) but I will not be able to do that easily with branch 1.x, so I hope sonatype will propose an alternative.
More details available at : https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6199

I also contact maven central support (by mail because there is no code repository OR bug tracker .... 😑 ...) about adding a way to skip publishing ... (and also share concerns about their way to make open source ...) let see if we get an answer ...

For curious here is the email :

Hi,

I face an issue migrating from nexus-staging-maven-plugin to
central-publishing-maven-plugin.
I tried to open a ticket to report it ... and I found nothing ... no code
source repository, no bug tracker...

This is a so bad situation that community already created a fork :
https://github.com/mavenplugins/central-publishing-maven-plugin

For a tooling which is about publishing library (and mainly open source
one) ... this is funny that you didn't embrace open source culture...
The fact I need to contact you by mail instead of github or gitlab is
kind of ironic..
And also funny info reported in maven central about your plugin is bad ...
See : https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin
And try to click on Continuous Integration and Source Control ...
Both link go to nothing ...
I really hope that you will make this project a real open source one...
(also for security reason)

Anyway initially I wanted to report that issue.
I currently made the migration and I have difficulty to skip
publishing one of my module.

With previous nexus-staging-maven-plugin I was able to do that with
true...
So, I tried to use true from new
central-publishing-maven-plugin
And I face :

[ERROR] Failed to execute goal
org.sonatype.central:central-publishing-maven-plugin:0.9.0:publish
(injected-central-publishing) on project leshan-integration-tests: The
packaging for this project did not assign a file to the build artifact
-> [Help 1]

I also try with without success ..

I see that the community fork solve that problem with :
mavenplugins/central-publishing-maven-plugin#22

I hope you will take this use case into account and propose a release soon.

Regards,

Simon (Eclipse Commiiter)

@sonarqubecloud
Copy link
Copy Markdown

@sbernard31 sbernard31 merged commit 1b8c3f2 into master Nov 19, 2025
2 checks passed
@sbernard31 sbernard31 deleted the maven_central2 branch December 18, 2025 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant