Add maven-central publishing placeholder #124
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you describe the point of this change? |
|
Yes, sure I can! should I? |
|
updated the description 😃🤞🏻 |
|
I am a bit confused then. Did you not use JReleaser + the new Central Pulishing Portal for the 2 releases y'all did? Or did you just use JReleaser, but continue to use OSSRH? |
|
oh, ok yes... it's JReleaser + OSSRH. To switch to this central-publishing-api we'd need to request the migration (and from what it seems, it'll affect all the projects we publish, so the plan is to prepare all projects for JReleaser with OSSRH publishing. Then once all are ready, request the migration, switch the config from OSSRH to CentralPublishing and 🤞🏻) |
|
Ok, that's the bit I was missing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The thing is that the current config works fine for the OSSRH publishing. Once we switch to the maven-central publishing API we'd need that second config (
mavenCentral). So the idea @dreab8 and I had was to include the "placeholder" configs in the repositories withmavenCentralset toactive: NEVERand then once we switch, it'll be easier for whoever works on the change to apply it.