You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2017/02/08 15:12:30 UTC
improving semantic versioning checking in our builds
The semver checker we use ( https://github.com/jeluard/semantic-versioning )
says on it's github:
/This library is in dormant state and won't add any new feature. You might want
to consider japicmd <https://github.com/siom79/japicmp> instead./
I looked at the referenced link, and it looks a lot better - it has support for
multiple kinds of checking, and produces nice reports with all the details of
changes.
See for example the configuration example here:
https://github.com/siom79/japicmp/blob/master/src/site/markdown/MavenPlugin.md
and notice the variety of kinds of checks:
|<breakBuildOnModifications> <breakBuildOnBinaryIncompatibleModifications>
<breakBuildOnSourceIncompatibleModifications>
<breakBuildBasedOnSemanticVersioning> <breakBuildIfCausedByExclusion>
<onlyBinaryIncompatible>|
Perhaps we should switch to using this one. What do others think?
-Marshall
Re: improving semantic versioning checking in our builds
Posted by Marshall Schor <ms...@schor.com>.
Here's a link to japicmp project, it's Apache 2.0 licensed :-)
http://siom79.github.io/japicmp/
Here's a link that shows the formatted report of changes it produces:
https://siom79.github.io/japicmp/japicmp/japicmp.html
-Marshall
On 2/8/2017 10:12 AM, Marshall Schor wrote:
> The semver checker we use ( https://github.com/jeluard/semantic-versioning )
> says on it's github:
>
> /This library is in dormant state and won't add any new feature. You might want
> to consider japicmd <https://github.com/siom79/japicmp> instead./
>
> I looked at the referenced link, and it looks a lot better - it has support for
> multiple kinds of checking, and produces nice reports with all the details of
> changes.
>
> See for example the configuration example here:
> https://github.com/siom79/japicmp/blob/master/src/site/markdown/MavenPlugin.md
> and notice the variety of kinds of checks:
>
> |<breakBuildOnModifications> <breakBuildOnBinaryIncompatibleModifications>
> <breakBuildOnSourceIncompatibleModifications>
> <breakBuildBasedOnSemanticVersioning> <breakBuildIfCausedByExclusion>
> <onlyBinaryIncompatible>|
>
> Perhaps we should switch to using this one. What do others think?
>
> -Marshall
>
>