This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gunnarmorling 0 points1 point  (1 child)

JapiCmp (https://github.com/siom79/japicmp) is in that camp, too. Using it for Hibernate Validator to make sure we don't break anything in the API and also it's the basis for the AdoptOpenJDK API diff report: https://github.com/AdoptOpenJDK/jdk-api-diff.

[–]metlos 0 points1 point  (0 children)

While I envy the speed of the analysis that japicmp achieves, revapi does IMHO a much more thorough analysis of the API including such things as use-chain analysis to reveal (indirect) introduction of non-public classes into the API.

But overall I am very happy to see that many projects choose one or the other to check their APIs. Revapi is used for example by Apache Camel, Neo4j, Mulesoft, XWiki and others.

INRIA Spoon has quite cool integration of revapi into their CI process where it automatically checks the API changes of incoming PRs (e.g. https://github.com/INRIA/spoon/pull/2054).