Migrate to central-publishing-maven-plugin.
#491
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
copybara-service
bot
force-pushed
the
test_785997601
branch
from
9a8036e to
f58a406
Compare
This is like cl/782079419 but for our other projects. (Specifically, I covered Guava and all the projects with `pom.xml` files that I'm used to updating for a new Guava release. I haven't tried to find any projects we run _without_ Guava dependencies (if any) or any that use Bazel instead of Maven.) As in the previous CL, I have updated the GitHub CI repository secrets as described in https://central.sonatype.org/publish/generate-portal-token/, **but** I have done so only for projects where I have deployment permission (specifically, Compile-Testing, Guava, and Truth). The others (Auto and Caliper) will need to be updated by someone who has publication permission for those projects. (Actually, it looks like Caliper doesn't actually deploy CI snapshots, even though it seems to have Sonatype credentials saved in GitHub. Hmm.) And CI snapshot releases aside, anyone who wants to deploy a "true" release will need to enter a token into `~/.m2/settings.xml`, again as discussed in cl/782079419. RELNOTES=n/a PiperOrigin-RevId: 786033817
copybara-service
bot
force-pushed
the
test_785997601
branch
from
f58a406 to
c77a9ae
Compare
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.
Migrate to
central-publishing-maven-plugin.This is like cl/782079419 but for our other projects. (Specifically, I covered Guava and all the projects with
pom.xmlfiles that I'm used to updating for a new Guava release. I haven't tried to find any projects we run without Guava dependencies (if any) or any that use Bazel instead of Maven.)As in the previous CL, I have updated the GitHub CI repository secrets as described in https://central.sonatype.org/publish/generate-portal-token/, but I have done so only for projects where I have deployment permission (specifically, Compile-Testing, Guava, and Truth). The others (Auto and Caliper) will need to be updated by someone who has publication permission for those projects. (Actually, it looks like Caliper doesn't actually deploy CI snapshots, even though it seems to have Sonatype credentials saved in GitHub. Hmm.) And CI snapshot releases aside, anyone who wants to deploy a "true" release will need to enter a token into
~/.m2/settings.xml, again as discussed in cl/782079419.RELNOTES=n/a