Skip to content

Maven Central documentation is stale #36029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
jsoref opened this issue Jan 22, 2025 · 6 comments
Closed
1 task done

Maven Central documentation is stale #36029

jsoref opened this issue Jan 22, 2025 · 6 comments
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue needs SME This proposal needs review from a subject matter expert waiting for review Issue/PR is waiting for a writer's review

Comments

@jsoref
Copy link
Contributor

jsoref commented Jan 22, 2025

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-java-packages-with-maven

What part(s) of the article would you like to see updated?

All mentions of OSSRH and oss.sonatype.org should be updated, or a section section/page should be added.

https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#publishing

If you use https://oss.sonatype.org or https://s01.sonatype.org to publish, you are publishing via the Legacy OSSRH service. If you are publishing via a build tool integration, this might be configured as a default, so check the plugin's documentation to be sure, if you didn't manually specify a URL.

Apparently Maven Central is now a new thing which is something other than OSSRH.

Additional information

As I'm trying to set up publishing to Maven Central. Apparently that was replaced in mid 2024.

As I have no idea how to do it and can't really figure it out, I can't give particularly good information about how to fix this page, but at the very least a warning could be added:

Warning

This page is out of date and refers to the Legacy OSSRH Service.
@jsoref jsoref added the content This issue or pull request belongs to the Docs Content team label Jan 22, 2025
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 22, 2025
@nguyenalex836
Copy link
Contributor

@jsoref Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

@nguyenalex836 nguyenalex836 added actions This issue or pull request should be reviewed by the docs actions team waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Jan 22, 2025
@subatoi subatoi added the needs SME This proposal needs review from a subject matter expert label Jan 23, 2025
@github-actions GitHub Actions
Copy link
Contributor

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀

@subatoi
Copy link
Contributor

subatoi commented Feb 14, 2025

@jsoref 👋 I'm going to transfer this to an internal issue to fix it there. I'll update this issue when that's complete. Thank you for raising it!

@subatoi subatoi added the fix-internally Triggers a workflow to copy the issue internally and close the current issue label Feb 14, 2025
@docs-bot
Copy link
Collaborator

Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.

@subatoi
Copy link
Contributor

subatoi commented Feb 24, 2025

Just to follow up: this article now contains a warning. Many thanks for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue needs SME This proposal needs review from a subject matter expert waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jsoref @subatoi @docs-bot @nguyenalex836 and others