From 930d9500bda5ddf9f16c2573162adf1563787f6a Mon Sep 17 00:00:00 2001 From: cpovirk Date: Thu, 2 Oct 2025 12:24:47 -0700 Subject: [PATCH] Standardize on the ID "`attach-javadocs`" for `maven-javadoc-plugin`. Currently, our projects use a mix of that and "`attach-docs`." I think that the choice of ID is unlikely to make a difference in practice as long as we're consistent between a project and its parent (as was _not_ the case in jimfs prior to cl/814204365), but it's not hard to imagine messing things up someday if we copy and paste across projects. "`attach-javadocs`" does seem to be at least [some kind of recommendation](https://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#:~:text=attach%2Djavadocs). Also, in Guava: In the `future` projects, remove some probably needless differences in configuration that we'd carried over from the main Guava projects back in the day: ``` generate-javadoc-site-report site ``` I already removed that configuration from the main Guava projects back in cl/572593797. RELNOTES=n/a PiperOrigin-RevId: 814338191 --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 1e120d37..727f7d26 100644 --- a/pom.xml +++ b/pom.xml @@ -135,7 +135,7 @@ 3.12.0 - attach-docs + attach-javadocs jar