Apply Hanuman aggressive remediation

.github/pull_request_template.md

@@ -24,7 +24,8 @@ Before you push a pull request, review this list:
 - [ ] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
 - [ ] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI).
 - [ ] I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute?
-- [ ] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself.
+- [ ] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `./mvnw`; that's `./mvnw` on the command line by itself.
+      On Windows, run `mvnw.cmd`.
 - [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice.
 - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
 - [ ] Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process.

.github/workflows/maven.yml

@@ -46,7 +46,9 @@ jobs:
         persist-credentials: false
     - uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae  #v5.0.5
       with:
-        path: ~/.m2/repository
+        path: |
+          ~/.m2/repository
+          ~/.m2/wrapper
         key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
         restore-keys: |
           ${{ runner.os }}-maven-
@@ -56,4 +58,4 @@ jobs:
         distribution: ${{ runner.os == 'macOS' && matrix.java == '8' && 'zulu' || 'temurin' }}
         java-version: ${{ matrix.java }}
     - name: Build with Maven
-      run: mvn --errors --show-version --batch-mode --no-transfer-progress -Ddoclint=all
+      run: ./mvnw --errors --show-version --batch-mode --no-transfer-progress -Ddoclint=all

.gitignore

@@ -5,7 +5,9 @@ maven-eclipse.xml
 build.properties
 site-content
 *~
-.mvn/
+.mvn/*
+!.mvn/wrapper/
+!.mvn/wrapper/maven-wrapper.properties
 
 # IntelliJ IDEA files
 .idea

.mvn/wrapper/maven-wrapper.properties

@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#      https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+wrapperVersion=3.3.4
+distributionType=only-script
+distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.12/apache-maven-3.9.12-bin.zip

CONTRIBUTING.md

@@ -71,7 +71,8 @@ Making Changes
   + Create minimal diffs - disable _On Save_ actions like _Reformat Source Code_ or _Organize Imports_. If you feel the source code should be reformatted create a separate PR for this change first.
 + Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible but is a best practice.
 Unit tests are typically in the `src/test/java` directory.
-+ Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself.
++ Run a successful build using the default [Maven](https://maven.apache.org/) goal with `./mvnw`; that's `./mvnw` on the command line by itself.
+  On Windows, run `mvnw.cmd`.
 + Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
 + Each commit in the pull request should have a meaningful subject line and body. Note that commits might be squashed by a maintainer on merge.
 

README.md

@@ -83,10 +83,11 @@ Alternatively, you can pull it from the central Maven repositories:
 Building
 --------
 
-Building requires a Java JDK and [Apache Maven](https://maven.apache.org/).
+Building requires a Java JDK. Use the included Maven Wrapper to download and run [Apache Maven](https://maven.apache.org/).
 The required Java version is found in the `pom.xml` as the `maven.compiler.source` property.
 
-From a command shell, run `mvn` without arguments to invoke the default Maven goal to run all tests and checks.
+From a command shell, run `./mvnw` without arguments to invoke the default Maven goal to run all tests and checks.
+On Windows, run `mvnw.cmd`.
 
 Contributing
 ------------
@@ -96,9 +97,9 @@ There are some guidelines which will make applying PRs easier for us:
 + No tabs! Please use spaces for indentation.
 + Respect the existing code style for each file.
 + Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
-+ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
-+ Before you push a PR, run `mvn` (without arguments). This runs the default goal which contains all build checks.
-+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
++ Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `./mvnw`.
++ Before you push a PR, run `./mvnw` (without arguments). This runs the default goal which contains all build checks.
++ To see the code coverage report, regardless of coverage failures, run `./mvnw clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
 
 If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
 You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).