Bump the metadata group across 1 directory with 9 updates

[dependabot]

Bumps the metadata group with 9 updates in the /metadata directory:

Package	From	To
com.google.guava:guava	32.1.2-jre	33.2.1-jre
com.ibm.icu:icu4j	73.2	75.1
com.google.protobuf:protobuf-java	3.24.0	4.27.3
com.google.auto.value:auto-value	1.10.2	1.11.0
com.google.auto.value:auto-value-annotations	1.10.2	1.11.0
com.google.truth:truth	1.1.5	1.4.4
com.google.truth.extensions:truth-java8-extension	1.0.1	1.4.4
org.apache.maven.plugins:maven-compiler-plugin	3.8.1	3.13.0
org.apache.maven.plugins:maven-javadoc-plugin	3.5.0	3.8.0

Updates com.google.guava:guava from 32.1.2-jre to 33.2.1-jre

Release notes

Sourced from com.google.guava:guava's releases.

33.2.1

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.2.1-jre</version>
  <!-- or, for Android: -->
  <version>33.2.1-android</version>
</dependency>

Jar files

• 33.2.1-jre.jar
• 33.2.1-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 33.2.1-jre
• 33.2.1-android

JDiff

• 33.2.1-jre vs. 33.2.0-jre
• 33.2.1-android vs. 33.2.0-android
• 33.2.1-android vs. 33.2.1-jre

Changelog

• net: Changed InetAddress-String conversion methods to preserve the IPv6 scope ID if present. The scope ID can be necessary for IPv6-capable devices with multiple network interfaces. However, preserving it can also lead to problems for callers that rely on the returned values not to include the scope ID:
  • Callers might compensate for the old behavior of the methods by appending the scope ID to a returned string themselves. If so, you can update your code to stop doing so at the same time as you upgrade Guava. Of, if your code might run against multiple versions of Guava, you can check whether Guava has included a scope ID before you add one yourself.
  • Callers might pass the returned string to another system that does not understand scope IDs. If so, you can strip the scope ID off, whether by truncating the string form at a % character (leaving behind any trailing ] character in the case of forUriString) or by replacing the returned InetAddress with a new instance constructed by calling InetAddress.getByAddress(addr).
  • java.net.InetAddress validates any provided scope ID against the interfaces available on the machine. As a result, methods in InetAddresses may now fail if the scope ID fails validation.
    • Notable cases in which this may happen include:
      • if the code runs in an Android app without networking permission
      • if code passes InetAddress instances or strings across devices
    • If this is not the behavior that you want, then you can strip off the scope ID from the input string before passing it to Guava, as discussed above. (3f61870ac6)

33.2.0

Android users: Please test recent Guava versions

If you know of Guava Android users who have not yet upgraded to at least release 33.0.0, please encourage them to upgrade, preferably to today's release, 33.2.0. These releases have begun adding Java 8+ APIs to guava-android. While we don't anticipate problems, we do anticipate that any unexpected problems could force a disruptive rollback. To minimize any disruption, we'd like to catch any such problems early.

Please let us know of any problems you encounter.

Maven

... (truncated)

Commits

• See full diff in compare view

Updates com.ibm.icu:icu4j from 73.2 to 75.1

Release notes

Sourced from com.ibm.icu:icu4j's releases.

ICU 75.1

Unicode® ICU 75 updates to CLDR 45 (beta blog) locale data with new locales and various additions and corrections. C++ code now requires C++17 and is being made more robust.

The CLDR MessageFormat 2.0 specification is now in technology preview, together with a corresponding update of the ICU4J (Java) tech preview and a new ICU4C (C++) tech preview.

For details, please see https://icu.unicode.org/download/75.

ICU 75 RC

We are pleased to announce the release candidate for Unicode® ICU 75. It updates to CLDR 45 (alpha blog) locale data with new locales and various additions and corrections. C++ code now requires C++17 and is being made more robust.

The CLDR MessageFormat 2.0 specification is now in technology preview, together with a corresponding update of the ICU4J (Java) tech preview and a new ICU4C (C++) tech preview.

For details, please see https://icu.unicode.org/download/75.

Please test this release candidate on your platforms and report bugs and regressions by Monday, 2024-apr-15, via the icu-support mailing list, and/or please find/submit error reports.

Please do not use this release candidate in production.

The preliminary API reference documents are published on unicode-org.github.io/icu-docs/ – follow the “Dev” links there.

ICU 74.2 updates to CLDR 44.1 locale data. These are maintenance releases for ICU 74 and CLDR 44, with limited sets of bug fixes and no API or structural changes.

• The CLDR bug fix relevant for ICU is for some formatting patterns that erroneously had two adjacent space characters. These are coalesced into one. (CLDR-17233)
• Important: DateFormat.getInstanceForSkeleton() and the DateTimePatternGenerator sometimes used the wrong patterns because they failed to use/inherit certain data (ICU-22575 — CLDR 44 had removed some redundant data that ICU relied on)

For details, please see https://icu.unicode.org/download/74.

ICU 74.1

Unicode® ICU 74 updates to Unicode 15.1, and to CLDR 44 locale data with various additions and corrections.

ICU 74 and CLDR 44 are major releases, including a new version of Unicode and major locale data improvements. They subsume the changes for the ICU 73.2 and CLDR 43.1 maintenance releases.

Unicode 15.1 adds source code security mechanisms, improves line breaking for southeast Asian scripts, and adds important CJK unified ideographs.

CLDR 44 has added or improved data for a number of languages that have been newly added to ICU, and has improved measurement unit handling, conversion, and formatting.

ICU 74 implements these improvements, adds new C APIs for locale handling, adds a plug-in API for word segmentation, and switches the Java build system to Maven.

For details, please see https://icu.unicode.org/download/74.

ICU 74 RC

We are pleased to announce the release candidate for Unicode® ICU 74. It updates to Unicode 15.1, and to CLDR 44 locale data with various additions and corrections.

ICU 74 and CLDR 44 are major releases, including a new version of Unicode and major locale data improvements. They subsume the changes for the ICU 73.2 and CLDR 43.1 maintenance releases.

For details, please see https://icu.unicode.org/download/74.

Please test this release candidate on your platforms and report bugs and regressions by Wednesday, 2023-oct-26, via the icu-support mailing list, and/or please find/submit error reports.

Please do not use this release candidate in production.

... (truncated)

Commits

• See full diff in compare view

Updates com.google.protobuf:protobuf-java from 3.24.0 to 4.27.3

Commits

• See full diff in compare view

Updates com.google.auto.value:auto-value from 1.10.2 to 1.11.0

Release notes

Sourced from com.google.auto.value:auto-value's releases.

AutoValue 1.11.0

What's Changed

• AutoValue (including AutoBuilder) no longer bundles the Kotlin metadata API. This may require adding an explicit dependency on org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.9.0 or org.jetbrains.kotlin:kotlin-metadata-jvm:2.0.0 to client code that uses AutoBuilder to build Kotlin classes. The metadata API has changed from kotlinx.metadata to kotlin.metadata, but AutoBuilder uses reflection to function with either. (260b61ec7)
• Support for generating Java 7 code has been removed from AutoValue, AutoAnnotation, and AutoBuilder. You must be on at least Java 8, or an Android version with desugaring that allows it to pass for Java 8. 1.10.4 is the last AutoValue version with support for Java 7. (b9142b7cd)
• AutoBuilder now reports an error if it encounters a @Nullable primitive parameter. Primitive types cannot be null, and should not be annotated for nullness. (7cbdeb43b)
• Annotations on type parameters, like abstract @Nullable T foo(), are now better propagated to fields and constructor parameters. (92d881ed9)
• The generated toBuilder() method now says new AutoValue_Foo.Builder(this) rather than just new Builder(this), to do the right thing if an extension generates its own subclass of Builder. (324470ba2)
• The "copy constructor" in a generated Builder is no longer private. (6730615c9)
• Added support for extending AutoValue.Builder with abstract methods. (7d4b020dd)
• The annotation processors now support all kinds of resource URLs when loading template resources. This change only affects the case where the AutoValue (etc) processors are being invoked in an unusual environment, for example from a GraalVM app. It does not affect code that is merely being compiled for such an environment. (80b0ada75)

Full Changelog: google/auto@auto-value-1.10.4...auto-value-1.11.0

AutoValue 1.10.4

• A workaround for a JDK bug with reading jar resources has been extended so it always applies, rather than just as a fallback. See #1572. (3f69cd255)
• If an AutoValue property method is @Nullable, the corresponding field in the generated class will be too. This was already the case for TYPE_USE @Nullable or if the method had @CopyAnnotations, but now @Nullable will be copied in other cases too. (4506804f1)

AutoValue 1.10.3

• An "incompatible version" issue with Kotlin compilation has been fixed. See #1574. (b21c7f4fb)
• A warning is now produced if a setX method in a Builder or its return type is marked @Nullable. Those methods always return the Builder instance, which is never null. (e5b4b5484)

Commits

• 5e02d64 Set version number for auto-value-parent to 1.11.0.
• 80b0ada Support all kinds of resource URLs when loading template resources.
• 260b61e Use reflection to avoid referencing the Kotlin metadata API directly.
• 76be89a Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /fa...
• c11484e Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /value
• b21d69d Bump kotlin.version from 1.9.24 to 2.0.0 in /value
• e55e60a Update AutoValue to reflect recent Kotlin Metadata API changes.
• 29f739b Bump actions/checkout from 4.1.5 to 4.1.6
• 199a727 Bump kotlin.version from 1.9.23 to 1.9.24 in /value
• f2b22e3 Bump actions/checkout from 4.1.4 to 4.1.5
• Additional commits viewable in compare view

Updates com.google.auto.value:auto-value-annotations from 1.10.2 to 1.11.0

Release notes

Sourced from com.google.auto.value:auto-value-annotations's releases.

AutoValue 1.11.0

What's Changed

• AutoValue (including AutoBuilder) no longer bundles the Kotlin metadata API. This may require adding an explicit dependency on org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.9.0 or org.jetbrains.kotlin:kotlin-metadata-jvm:2.0.0 to client code that uses AutoBuilder to build Kotlin classes. The metadata API has changed from kotlinx.metadata to kotlin.metadata, but AutoBuilder uses reflection to function with either. (260b61ec7)
• Support for generating Java 7 code has been removed from AutoValue, AutoAnnotation, and AutoBuilder. You must be on at least Java 8, or an Android version with desugaring that allows it to pass for Java 8. 1.10.4 is the last AutoValue version with support for Java 7. (b9142b7cd)
• AutoBuilder now reports an error if it encounters a @Nullable primitive parameter. Primitive types cannot be null, and should not be annotated for nullness. (7cbdeb43b)
• Annotations on type parameters, like abstract @Nullable T foo(), are now better propagated to fields and constructor parameters. (92d881ed9)
• The generated toBuilder() method now says new AutoValue_Foo.Builder(this) rather than just new Builder(this), to do the right thing if an extension generates its own subclass of Builder. (324470ba2)
• The "copy constructor" in a generated Builder is no longer private. (6730615c9)
• Added support for extending AutoValue.Builder with abstract methods. (7d4b020dd)
• The annotation processors now support all kinds of resource URLs when loading template resources. This change only affects the case where the AutoValue (etc) processors are being invoked in an unusual environment, for example from a GraalVM app. It does not affect code that is merely being compiled for such an environment. (80b0ada75)

Full Changelog: google/auto@auto-value-1.10.4...auto-value-1.11.0

AutoValue 1.10.4

• A workaround for a JDK bug with reading jar resources has been extended so it always applies, rather than just as a fallback. See #1572. (3f69cd255)
• If an AutoValue property method is @Nullable, the corresponding field in the generated class will be too. This was already the case for TYPE_USE @Nullable or if the method had @CopyAnnotations, but now @Nullable will be copied in other cases too. (4506804f1)

AutoValue 1.10.3

• An "incompatible version" issue with Kotlin compilation has been fixed. See #1574. (b21c7f4fb)
• A warning is now produced if a setX method in a Builder or its return type is marked @Nullable. Those methods always return the Builder instance, which is never null. (e5b4b5484)

Commits

• 5e02d64 Set version number for auto-value-parent to 1.11.0.
• 80b0ada Support all kinds of resource URLs when loading template resources.
• 260b61e Use reflection to avoid referencing the Kotlin metadata API directly.
• 76be89a Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /fa...
• c11484e Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /value
• b21d69d Bump kotlin.version from 1.9.24 to 2.0.0 in /value
• e55e60a Update AutoValue to reflect recent Kotlin Metadata API changes.
• 29f739b Bump actions/checkout from 4.1.5 to 4.1.6
• 199a727 Bump kotlin.version from 1.9.23 to 1.9.24 in /value
• f2b22e3 Bump actions/checkout from 4.1.4 to 4.1.5
• Additional commits viewable in compare view

Updates com.google.truth:truth from 1.1.5 to 1.4.4

Release notes

Sourced from com.google.truth:truth's releases.

v1.4.4

• Annotated the rest of the main package for nullness, and moved the @NullMarked annotation from individual classes up to the package to avoid a warning under --release 8. (e107aeadc)
• Improved the failure message for matches to conditionally suggest using containsMatch. (7e9fc7aec)

1.4.3

Known Issue for at least some builds targeting Java 8, fixed in 1.4.4: "unknown enum constant ElementType.MODULE": google/truth#1320. As far as we know, this is only a warning, so it should cause practical problems only if you use -Werror or you perform reflection on @NullMarked under a Java 8 runtime.

• Added more nullness information to our APIs (in the form of JSpecify annotations). This could lead to additional warnings (or even errors) for users of Kotlin and other nullness checkers. Please report any problems. (ee680cbaf)
• Deprecated Subject.Factory methods for Java 8 types. We won't remove them, but you can simplify your code by migrating off them: Just replace assertAbout(foos()).that(foo) with assertThat(foo) (or about(foos()).that(foo) with that(foo)). (59e7a5065)

1.4.2

This release is the final step of copying all our methods from Truth8 to Truth. If you have not already migrated your usages from Truth8 to Truth, you may see build errors:

OptionalSubjectTest.java:39: error: reference to assertThat is ambiguous
    assertThat(Optional.of("foo")).isPresent();
    ^
  both method assertThat(@org.checkerframework.checker.nullness.qual.Nullable Optional<?>) in Truth8 and method assertThat(@org.checkerframework.checker.nullness.qual.Nullable Optional<?>) in Truth match

In most cases, you can migrate your whole project mechanically: git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'. (You can make that change before upgrading to Truth 1.4.2 or as part of the same commit.)

If you instead need to migrate your project incrementally (for example, because it is very large), you may want to upgrade your version of Truth incrementally, too, following our instructions for 1.3.0 and 1.4.0.

For help

Please feel welcome to open an issue to report problems or request help.

Changelog

• Removed temporary type parameters from Truth.assertThat(Stream) and Truth.assertThat(Optional). This can create build errors, which you can fix by replacing all your references to Truth8 with references to Truth. (45782bd0e)

1.4.1

This release deprecates Truth8.

All its methods have become available on the main Truth class. In most cases, you can migrate your whole project mechanically: git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'

While we do not plan to delete Truth8, we recommend migrating off it, at least if you static import assertThat: If you do not migrate, such static imports will become ambiguous in Truth 1.4.2, breaking your build.

1.4.0

In this release, our assertions on Java 8 types continue to move from the Truth8 class to the main Truth class. This change should not break compatibility for any supported JDK or Android version, even users who test under old versions of Android without API desugaring. Additionally, we will never break binary compatibility, though some users will have to make changes to their source code in order for it to compile against newer versions.

This release is likely to lead to more build failures than 1.3.0 did. However, those failures should be straightforward to fix.

Example build failure

Foo.java:152: error: reference to assertThat is ambiguous
    assertThat(repo.findFileWithName("foo")).isNull();
</tr></table> 

... (truncated)

Commits

• ddeaa0c Set version number for truth-parent to 1.4.4.
• e107aea Annotate the rest of the main package (basically just the Java 8 subjects) fo...
• 8ac91a6 Document that truth-java8-extension is obsolete.
• 99af8be Bump org.codehaus.mojo:animal-sniffer-maven-plugin from 1.23 to 1.24 in the d...
• 54e548c Bump the dependencies group with 2 updates
• 2183a14 Migrate from legacy com.google.gwt to org.gwtproject.
• 7e9fc7a Make StringSubject.matches suggest using containsMatch if matches(x) fails bu...
• af140d6 Fix grammar in Javadoc comments.
• afda443 Annotate formattingDiffsUsing methods as supporting nullable element/value ...
• ee680cb Use JSpecify annotations in the public release.
• Additional commits viewable in compare view

Updates com.google.truth.extensions:truth-java8-extension from 1.0.1 to 1.4.4

Updates org.apache.maven.plugins:maven-compiler-plugin from 3.8.1 to 3.13.0

Release notes

Sourced from org.apache.maven.plugins:maven-compiler-plugin's releases.

3.13.0

🚀 New features and improvements

• [MCOMPILER-574] - Propagate cause of exception in AbstractCompilerMojo (#232) @​slawekjaranowski
• [MCOMPILER-582] - Automatic detection of release option for JDK < 9 (#228) @​slawekjaranowski
• [MCOMPILER-583] - Require Maven 3.6.3 (#229) @​slawekjaranowski
• [MCOMPILER-577] - Rename parameter "forceJavacCompilerUse" (#225) @​kwin
• [MCOMPILER-570] - Add links to javac documentation of JDK17 (#224) @​kwin
• [MCOMPILER-576] - Deprecate parameter "compilerVersion" (#223) @​kwin

📦 Dependency updates

• [MCOMPILER-575] - Bump plexusCompilerVersion from 2.14.2 to 2.15.0 (#227) @​dependabot
• Bump apache/maven-gh-actions-shared from 3 to 4 (#226) @​dependabot

📝 Documentation updates

• [MCOMPILER-548] - JDK 21 throws annotations processing warning that can not be turned off (#200) @​hgschmie

👻 Maintenance

• [MCOMPILER-584] - Refresh page - Using Non-Javac Compilers (#231) @​slawekjaranowski
• [MCOMPILER-585] - Refresh plugins versions in ITs (#230) @​slawekjaranowski
• subject verb agreement (#221) @​elharo

3.12.1

🐛 Bug Fixes

• [MCOMPILER-567] - Fail to compile if the generated-sources/annotation… (#218) @​jorsol

📦 Dependency updates

• [MCOMPILER-568] - Bump plexusCompilerVersion from 2.14.1 to 2.14.2 (#220) @​dependabot

3.12.0

🚀 New features and improvements

• [MCOMPILER-562] - Add property maven.compiler.outputDirectory to CompilerMojo (#213) @​jGauravGupta
• [MCOMPILER-381] - Refactor incremental detection (#181) @​jorsol
• [MCOMPILER-542] - Clean JDK patch version in module-info.class (#208) @​jorsol
• [MCOMPILER-558] - compileSourceRoots in testCompile should be writable (#209) @​lorenzsimon
• [MCOMPILER-559] - Warn if overwriting the project's artifact's file to a different value (#211) @​gnodet
• [MCOMPILER-550] - make outputDirectory writable (#202) @​bmarwell
• [MCOMPILER-549] - Improve log message in case of recompilation - fix jenkins build (#203) @​slawekjaranowski
• [MCOMPILER-549] - Improve log message in case of recompilation (#201) @​BrowneMonke
• [MCOMPILER-391] - Use dep mgmt when resolving annotation processors and their deps (#180) @​psiroky
• [MCOMPILER-531] - Prepare for Java 20(-ea) (#184) @​slachiewicz

... (truncated)

Commits

• a1415aa [maven-release-plugin] prepare release maven-compiler-plugin-3.13.0
• b2b9196 [MCOMPILER-574] Propagate cause of exception in AbstractCompilerMojo
• 6d2ce5a [MCOMPILER-584] Refresh page - Using Non-Javac Compilers
• eebad60 [MCOMPILER-585] Refresh plugins versions in ITs
• ceacf68 [MCOMPILER-582] Automatic detection of release option for JDK < 9
• 110293f [MCOMPILER-583] Require Maven 3.6.3
• 90131df [MCOMPILER-575] Bump plexusCompilerVersion from 2.14.2 to 2.15.0 (#227)
• 74cfc72 [MCOMPILER-548] JDK 21 throws annotations processing warning that can not be ...
• f85aa27 Bump apache/maven-gh-actions-shared from 3 to 4
• d59ef49 extract Maven 3.3.1 specific method call
• Additional commits viewable in compare view

Updates org.apache.maven.plugins:maven-javadoc-plugin from 3.5.0 to 3.8.0

Release notes

Sourced from org.apache.maven.plugins:maven-javadoc-plugin's releases.

3.7.0

• [MJAVADOC-795] - Upgrade to Parent 42 and Maven 3.6.3 (#281) @​michael-o
• [MJAVADOC-682] - Reactor builds fail when multiple modules with same gr… (#253) @​michael-o
• directory, not folder (#252) @​michael-o
• [MJAVADOC-782] - Align read-only parameters naming with other plugins (#251) @​michael-o
• [MJAVADOC-781] - Upgrade plugins and components (in ITs) (#250) @​michael-o
• [MJAVADOC-780] - add missing plugin configuration (#249) @​hboutemy

📦 Dependency updates

• Bump org.apache.maven.shared:maven-invoker from 3.2.0 to 3.3.0 (#283) @​dependabot
• Bump org.assertj:assertj-core from 3.25.3 to 3.26.0 (#282) @​dependabot
• Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2 (#271) @​dependabot
• Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0 (#277) @​dependabot
• Bump commons-io:commons-io from 2.16.0 to 2.16.1 (#276) @​dependabot
• [MJAVADOC-789] - Bump org.codehaus.plexus:plexus-interactivity-api from 1.2 to 1.3 (#268) @​dependabot
• [MJAVADOC-788] - Bump commons-io:commons-io from 2.15.1 to 2.16.0 (#273) @​dependabot
• Bump apache/maven-gh-actions-shared from 3 to 4 (#270) @​dependabot
• Bump com.thoughtworks.qdox:qdox from 2.0.3 to 2.1.0 (#266) @​dependabot
• Bump org.assertj:assertj-core from 3.25.1 to 3.25.3 (#269) @​dependabot
• Bump org.codehaus.plexus:plexus-interactivity-api from 1.1 to 1.2 (#258) @​dependabot
• Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1 (#263) @​dependabot
• Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (#260) @​dependabot
• Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (#262) @​dependabot
• Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1 (#256) @​dependabot
• Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (#257) @​dependabot
• Bump commons-io:commons-io from 2.15.0 to 2.15.1 (#254) @​dependabot

📝 Documentation updates

• Fix addStylesheets Javadoc (#261) @​scordio

👻 Maintenance

• Bump org.springframework:spring-context from 4.3.29.RELEASE to 5.2.21.RELEASE in /src/it/projects/MJAVADOC-434_fixcompile (#280) @​dependabot
• Exclude JDK 8 - temurin, adopt-openj9 on macos (#279) @​slawekjaranowski

🔧 Build

• Fix build (#264) @​slawekjaranowski

3.6.2

🐛 Bug Fixes

• [MJAVADOC-716] - Fix stale files detection failing because of the newline (#144) @​gnodet
• [MJAVADOC-713] - Skipping Javadoc reportset leaves empty Javadoc link i… (#246) @​michael-o
• [MJAVADOC-762] - don't share state between tests (#218) @​elharo
• [MJAVADOC-726] - exclude velocity (#243) @​elharo

... (truncated)

Commits

• 621cba6 [maven-release-plugin] prepare release maven-javadoc-plugin-3.8.0
• eab964c [MJAVADOC-603] javadoc:fix failure on JDK10: java.lang.ClassNotFoundException...
• 0a26a7e Update since tags
• 08205b1 Add compile step for MJAVADOC-365 IT
• 4c8ca8e [MJAVADOC-804] Remove temporary directories created by tests
• 91369fa [MJAVADOC-775] Option 'taglets/taglet/tagletpath' ignored when pointing to a JAR
• be2fa20 [MJAVADOC-783] Invalid path when using TagletArtifact and TagletPath
• 3eb47c5 [MJAVADOC-791] maven-javadoc-plugin not working correctly together with maven...
• d3afd39 [MJAVADOC-803] Add default parameter to force root locale
• 4904e08 [MJAVADOC-802] Set default value of defaultAuthor parameter in fix goals to $...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #3610.