Breaking binary compatibility should break the build instead of

generating a report one might skip reading, especially for PRs.

Author: garydgregory

.github/workflows/maven.yml

@@ -45,4 +45,4 @@ jobs:
       with:
         java-version: ${{ matrix.java }}
     - name: Build with Maven
-      run: mvn -V package --file pom.xml --no-transfer-progress
+      run: mvn -V --file pom.xml --no-transfer-progress

pom.xml

@@ -246,9 +246,6 @@ limitations under the License.
     <checkstyle.version>2.17</checkstyle.version>
     <commons.japicmp.version>0.15.1</commons.japicmp.version>
     <commons.jacoco.version>0.8.6</commons.jacoco.version>
-
-    <!-- generate report even if there are binary incompatible changes -->
-    <commons.japicmp.breakBuildOnBinaryIncompatibleModifications>false</commons.japicmp.breakBuildOnBinaryIncompatibleModifications>
     <japicmp.skip>false</japicmp.skip>
 
     <!-- Commons Release Plugin -->
@@ -261,7 +258,7 @@ limitations under the License.
     <commons.releaseManagerKey>BC87A3FD0A54480F0BADBEBD21939FF0CA2A6567</commons.releaseManagerKey>
   </properties>
   <build>
-    <defaultGoal>clean verify apache-rat:check clirr:check checkstyle:check javadoc:javadoc</defaultGoal>
+    <defaultGoal>clean install apache-rat:check japicmp:cmp checkstyle:check javadoc:javadoc</defaultGoal>
     <pluginManagement>
       <plugins>
         <plugin>