Added module that doesn't compile or test by default

Original approach would have caused an issue when releasing as version
would not get incremented in module.

Author: ashley-taylor

.github/workflows/test-lang-java.yml

@@ -75,8 +75,13 @@ jobs:
         run: ./build.sh lint
 
       - name: Test
+        if: matrix.java < 17
         run: ./build.sh test
 
+      - name: Test Java >= 17
+        if: matrix.java >= 17
+        run: ./build.sh testJava17
+
   interop:
     name: Java ${{ matrix.java }} Interop
     runs-on: ubuntu-latest
@@ -149,42 +154,3 @@ jobs:
       - name: Run Interop Tests
         working-directory: lang/java/ipc
         run: mvn -B test -P interop-data-test
-
-  testJava17:
-    name: Java ${{ matrix.java }} Test
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        java:
-        - '17'
-        - '18'
-        - '19'
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Cache Local Maven Repository
-        uses: actions/cache@v2
-        with:
-          path: ~/.m2/repository
-          key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
-          restore-keys: |
-            ${{ runner.os }}-maven-
-
-      - name: Setup Temurin JDK
-        if: matrix.java == '17'
-        uses: actions/setup-java@v2
-        with:
-          distribution: 'temurin'
-          java-version: ${{ matrix.java }}
-
-      - name: Setup Oracle JDK
-        if: matrix.java == '18' || matrix.java == '19'
-        uses: oracle-actions/setup-java@v1
-        with:
-          website: jdk.java.net
-          release: ${{ matrix.java }}
-          version: latest
-
-      - name: Run Interop Tests
-        working-directory: lang/java
-        run: mvn -B test -P java17

lang/java/build.sh

@@ -18,7 +18,7 @@
 set -e
 
 usage() {
-  echo "Usage: $0 {lint|test|dist|clean}"
+  echo "Usage: $0 {lint|test|testJava17|dist|clean}"
   exit 1
 }
 
@@ -35,6 +35,11 @@ main() {
         # Test the modules that depend on hadoop using Hadoop 2
         mvn -B test -Phadoop2
         ;;
+      testJava17)
+        mvn -DdisableJava17=false -B test
+        # Test the modules that depend on hadoop using Hadoop 2
+        mvn -B test -Phadoop2
+        ;;
       dist)
         mvn -P dist package -DskipTests javadoc:aggregate
         ;;

lang/java/java17-test/pom.xml

@@ -36,6 +36,9 @@
     <maven.compiler.target>17</maven.compiler.target>
     <maven.compiler.source>17</maven.compiler.source>
     <main.basedir>${project.parent.parent.basedir}</main.basedir>
+    <!-- by default we skip this but if the JAVA17 env variable is set then this check will no longer pass compiling and running the tests -->
+    <disableJava17>true</disableJava17>
+    
   </properties>
 
   <dependencies>
@@ -45,6 +48,32 @@
       <version>${project.version}</version>
     </dependency>
   </dependencies>
+  
+  <build>
+    <plugins>
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-deploy-plugin</artifactId>
+        <configuration>
+          <skip>true</skip>
+        </configuration>
+      </plugin>
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-compiler-plugin</artifactId>
+        <configuration>
+          <skip>${disableJava17}</skip>
+        </configuration>
+      </plugin>
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-surefire-plugin</artifactId>
+        <configuration>
+          <skip>${disableJava17}</skip>
+        </configuration>
+      </plugin>
+    </plugins>
+  </build>
 
 </project>
 

lang/java/pom.xml

@@ -86,6 +86,7 @@
     <module>grpc</module>
     <module>integration-test</module>
     <module>perf</module>
+    <module>java17-test</module>
   </modules>
 
   <build>
@@ -471,13 +472,6 @@
         <hadoop.version>2.10.1</hadoop.version>
       </properties>
     </profile>
-    <profile>
-      <id>java17</id>
-      <modules>
-	    <module>avro</module>
-      	<module>java17-test</module>
-      </modules>
-    </profile>
   </profiles>
 
   <!-- dependencyManagement can be used to define dependency versions, scopes, and