Japicmp Versions Save

• skip-Tag in plugin configuration and -Djapicmp.skip work #366
• Do not report any incompatibilities if class becomes public. #365

• The maven plugin runs with Java-16. This also made changes necessary to migrate to the maven-resolver-API. Hence; the japicmp-maven plugin only runs with maven >= 3.1.0 #275
• New change that is detected: METHOD_DEFAULT_ADDED_IN_IMPLEMENTED_INTERFACE. #267
• StdoutOutputGenerator does not print superclass if class itself has changed.

Available at Maven Central.

• No ArtifactNotFoundException when comparison list is build from maven project #278

Available at Maven Central.

• New annotations or new enums are no longer tracked as incompatible (regression) #279
• Updated guava version to 30.0-jre

Available at Maven Central.

• The post analysis script can be loaded from the classpath. #274
• Exceptions during the artifact resolution do no longer break the build if the artifact was found. #284
• Option ignoreNonResolvableArtifacts is evaluated correctly again. #283
• Workaround was added to support bundle packaging. #280

Available at Maven Central.

• Variable mavenProject in maven-plugin is read from MavenParameters and not from injected field. #128
• Moving protected field to superclass is no longer marked as binary incompatible. #132
• Maven plugin can be run without section. #134

Available at Maven Central.

• Declaration of <newVersion/> and <oldVersion/> should be optional. #129
• New parameter <oldVersionPattern/> allows filtering of automatically chosen old version. #129
• Better error message in case exception class could not be loaded from classpath. #130
• serialVersionUID is ignored for enums. #131

Available at Maven Central.

• maven plugin has new option to skip XML, HTML and diff report. #121
• maven-plugin has new option to ignore missing old version. #122
• Interface moved to abstract class is no longer reported to be source incompatible. #123
• When file for optional dependency could not be resolved the plugin does not break the build with 'could not resolve dependency...'. #125
• Improved output if build is broken due to found incompatibilities.

• Exceptions declared in method signatures are now tracked and evaluated regarding source incompatibility. #110
• HTML report now names all incompatible changes additional to the markers * and !. #115
• Maven plugin has new parameter postAnalysisScript that allows execution of Groovy script after comparison phase. #120
• Method added to new interface is no longer detected as source incompatible. #112
• Method that overrides in subinterface method from superinterface is no longer detected as source incompatible. #113
• Excluded xerces vom maven-reporting dependency in order to prevent warnings from SAXParserImpl. #109
• Indirectly implemented interfaces are no longer reported as removed. #119

• japicmp now also supports tracking of source incompatible changes. #59
• The XML report now also outputs the reason for each change for better traceability. #105
• The maven plugin comes now with the new option breakBuildBasedOnSemanticVersioning that breaks the build based on the version numbers of the old and new archive(s) assuming they are using semantic versioning. #108
• The maven plugin now has a new option packagingSupported that lets you define for which packaging types the plugin shoule be invoked. This is useful when the plugin is defined in the root pom and should be executed for all submodules, but you want to exclude some of these submodules by packaging type. #100
• Fixed NPE in JavadocLikePackageFilter when matching against classes in the default (empty) package. #106