From 084e36597a04dfdb0195e5b82a1b036a20bc45e2 Mon Sep 17 00:00:00 2001 From: cpovirk Date: Tue, 11 Nov 2025 12:31:21 -0800 Subject: [PATCH] Rip out `maven-release-plugin` configuration. As best I can tell, this configuration has never offered anything over what we get by default from `maven-deploy-plugin` (or its modern replacement, `central-publishing-maven-plugin`). I wouldn't rule out that we've never actually used `maven-release-plugin` at all for our releases: We may have been running `mvn deploy` instead of `mvn release:prepare` + `mvn release:perform`. (Certainly the script that we use for most of our projects uses `mvn deploy` directly.) I looked into the `-DenableCiProfile` bit, and as best I can tell, we've never defined a property by that name, nor is it a standard part of Maven. I do see one defined in [the `pom.xml` for `maven-surefire-plugin`](https://central.sonatype.com/artifact/org.apache.maven.plugins/maven-surefire-plugin/3.1.0), but our setting the flag would have no effect on our _usage_ of Surefire; the setting there would matter only when _building_ Surefire. Anyway, this configuration dates back to cl/30835352 (Caliper) and cl/51674256 (Compile-Testing). I can't fully rule out that it's doing _something_ for _some_ process that _someone_ uses, but I'm highly comfortable removing it. We can always roll back if we somehow see trouble, and I don't expect any trouble in the first place. RELNOTES=n/a PiperOrigin-RevId: 831024758 --- pom.xml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/pom.xml b/pom.xml index 2b3cf230..350553b2 100644 --- a/pom.xml +++ b/pom.xml @@ -118,14 +118,6 @@ - - maven-release-plugin - 3.2.0 - - sonatype-oss-release - deploy - - maven-jar-plugin 3.4.2