You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix some problems with the Central Publishing Portal setup after cl/786033817:
- Stop inheriting from `oss-parent` in `guava-bom`. I'm seeing `guava-bom` try to deploy to the old `oss.sonsatype.org`, even as the other subprojects successful deploy to `central.sonatype.com`, and I believe that's a result of the parent. I put in the new Central config to compensate. (I don't remember if we have a good reason for `guava-bom` to not inherit from `guava-parent`, but I figure there's some chance we do. I could look into it.)
- Skip `central-publishing-maven-plugin` for `guava-tests`, just as we did for `maven-deploy-plugin`. I haven't seen evidence that this is a problem yet, but that may be only because:
- We've attempted only snapshot releases, not "full" releases? I think that some problems "like this" have appeared only during validation of full releases, at least historically.
- The snapshot release failed before it even got to `guava-tests`.
- Avoid mentioning `maven-deploy-plugin` in `guava-tests` and even in our `pluginManagement`. We should no longer be using it, so we shouldn't need to specify a version.
- Remove entry for `sonatype-nexus-staging`. That entry may or may not actually be a "problem," but I'd meant to remove it in the previous CL for all our projects. I just missed Guava (because I started with a list of projects that _depend_ on Guava and then went back for Guava).
(Here's [the log for the failure](https://github.com/google/guava/actions/runs/16457531993/job/46518814913).)
RELNOTES=n/a
PiperOrigin-RevId: 786078646
0 commit comments