From a0ae8750a15caa0192b868df149062537b786bd6 Mon Sep 17 00:00:00 2001
From: Filip Hrisafov <filip.hrisafov@gmail.com>
Date: Thu, 1 Nov 2018 23:56:15 +0100
Subject: [PATCH] Adapt  japicmp-maven-plugin to not consider adding a new
 default method to an interface as incompatible

According to https://docs.oracle.com/javase/specs/jls/se8/html/jls-13.html#jls-13.5.3
Adding an abstract (default) method to an interface does not break compatibility with pre-existing binaries.
---
 parent/pom.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/parent/pom.xml b/parent/pom.xml
index 7ac85a46f..a30051d95 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -541,6 +541,14 @@
                         <parameter>
                             <oldVersionPattern>\d+\.\d+\.\d+\.Final</oldVersionPattern>
                             <breakBuildBasedOnSemanticVersioning>true</breakBuildBasedOnSemanticVersioning>
+                            <overrideCompatibilityChangeParameters>
+                                <overrideCompatibilityChangeParameter>
+                                    <compatibilityChange>METHOD_NEW_DEFAULT</compatibilityChange>
+                                    <binaryCompatible>true</binaryCompatible>
+                                    <sourceCompatible>false</sourceCompatible>
+                                    <semanticVersionLevel>MINOR</semanticVersionLevel>
+                                </overrideCompatibilityChangeParameter>
+                            </overrideCompatibilityChangeParameters>
                         </parameter>
                     </configuration>
                 </plugin>