spring-boot: Remove duplicate maven build (#324)

This PR removes the `pom.xml` and associated Maven commands from the
Spring Boot code sample, since we already have the Gradle build in the
same directory.

The Maven build is not monitored by Dependabot, so will slowly drift out
of sync with the Gradle definition. Removing the Maven build to match
what is done for the other Java sample, which only provides Gradle.
Rather than worrying about keeping both in sync, it's easier for us to
just provide 1 build system.

By submitting this pull request, I confirm that my contribution is made
under the terms of the MIT-0 license.

Author: danielfrankcom

.github/workflows/java-spring-boot-integ-tests.yml

@@ -16,40 +16,6 @@ on:
   workflow_dispatch:
 
 jobs:
-  test-maven:
-    runs-on: ubuntu-latest
-    permissions:
-      id-token: write # required by aws-actions/configure-aws-credentials
-    concurrency:
-      group: ${{ github.workflow }}
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v6
-
-      - name: Set up JDK 17
-        uses: actions/setup-java@v5
-        with:
-          java-version: "17"
-          distribution: "corretto"
-          architecture: x64
-          cache: maven
-
-      - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v5
-        with:
-          role-to-assume: ${{ secrets.JAVA_IAM_ROLE }}
-          aws-region: us-east-1
-
-      - name: Run Maven integration test
-        working-directory: ./java/spring_boot
-        env:
-          CLUSTER_USER: admin
-          CLUSTER_ENDPOINT: ${{ secrets.JAVA_SPRING_BOOT_CLUSTER_ENDPOINT }}
-          REGION: ${{ secrets.JAVA_SPRING_BOOT_CLUSTER_REGION }}
-          EXIT_AFTER_TEST: true
-        run: mvn spring-boot:run
-
   test-gradle:
     runs-on: ubuntu-latest
     permissions:

java/spring_boot/README.md

@@ -57,11 +57,8 @@ connections should be used where possible to ensure data security during transmi
    java -version
    ```
 
-* Build Tool (Maven or Gradle)
-    - _Maven_: Ensure Maven is installed if that is your preferred option. You can download it from
-      the [official website](https://maven.apache.org/download.cgi).
-    - _Gradle_: A Gradle wrapper is included with the example. If you prefer to use a system installation of Gradle, you
-      can download it from the [official website](https://gradle.org/install/).
+*  _Gradle_: A Gradle wrapper is included with the example. If you prefer to use a system installation of Gradle, you
+  can download it from the [official website](https://gradle.org/install/).
 * AWS SDK: Ensure that you set up the latest version of the AWS Java
   SDK from the [official website](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/setup.html).
 * You must have an Aurora DSQL cluster. For information about creating an Aurora DSQL cluster, see the
@@ -103,14 +100,6 @@ The example is designed to work with both admin and non-admin users:
 
 **Note:** running the example will use actual resources in your AWS account and may incur charges.
 
-**Using Maven:**
-
-```bash
-mvn spring-boot:run
-```
-
-**Using Gradle:**
-
 ```bash
 ./gradlew bootRun
 ```