That's certainly one use, but another use is for users making use of the APIs, so they can become aware of any changes.
re: checking the version number against semver - see the maven config options for the plugin, here: https://siom79.github.io/japicmp/MavenPlugin.html and look for the one you want (e.g. breakBuildBasedOnSemanticVersioning). -Marshall On 5/31/2017 5:31 PM, Richard Eckart de Castilho wrote: > On 31.05.2017, at 16:58, Marshall Schor <[email protected]> wrote: >> Not a blocker, but it seems if you think the api-change-report might be >> useful >> to your users, you might want to mention it in the what's new of the ReadMe, >> since it's a bit hidden (inside 3 separate folders). > To be honest, I consider the reports to be more a debugging help for the > case that the plugin fails the build because the version number wasn't > properly increased... or does the new API checking plugin not do this? > In that case, I would go back and also include the semver plugin again > into the build. > > -- Richard
