An API analyzer is the main interface one has to implement to support checking some kind of API.
A simple abstraction of a file or archive.
Extension of the archive interface that can also provide the version of the archive.
The instances of implementations of this interface are produced by the
A correspondence comparator deducer produces a comparator that is used to compare elements from 2 collections.
An element analyzer is basically a visitor over matching elements of some language between the two API versions being compared.
|DifferenceTransform<T extends Element>||
A difference transform may elect to transform certain kinds of differences into other kinds.
An element in a forest representation of given "language" under API inspection.
An element filter is a type of extension that can serve as an input filter on the element forest.
A representation of some "unit" understood by an API analyzer.
A reporter is the final stage during the API change analysis.
An analysis context is an aggregation of the APIs to check and configuration for the analysis.
Holds the result of the analysis.
Represents a set of archives that define an API.
Heavily inspired by the equivalently named class in Clirr 0.6.
Represents a single difference between an old and new API element.
This class represents the configuration of the Revapi analysis pipeline.
Represents the differences between comparable elements from old and new API.
The main entry point to the library.
This builder is merely a proxy to the
Because Revapi manages the lifecycle of instances of its extensions, it cannot unfortunately use the
Quick and dirty execution time statistics collection class.
Enumerates possible compatibility types.
Enumerates the possible severities of differences found during the API analysis.
Copyright © 2014-2020 Lukas Krejci. All Rights Reserved.