mkaouer / api-evolution-data-corpus

This corpus contains examples of "all" possible syntactic API changes in Java.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Overview

This project contains a corpus of data simulating API evolution in Java. The corpus include two versions of a library, which contain synthetic "dummy" API classes that have evolved between the version

Purpose

Backward compatibility is an issue to cope with today. To assess the backward compatibility, a lot of tools exist, but the question is how the tools perform. It is not easy to answear without a proper benchmark. Any benchmarks, however, need a test data. They are provided here.

Structure

The corpus contains two main directories: lib-v1 and lib-v2 with API examples in one version and its evolution in a following version. Each directory contains thousands of packages, where each package simulates one API change. The change is projected in the package name.

Directory client contains a simple client application that invokes API from the library. Its purpose is to simulate usage of the API.

Invocation

One can build the corpus simply by typing:

ant jar

It produces three JAR files: lib-v1.jar, lib-v2.jar and client.jar containing all API classes and the client compiled in byte-code.

The data may be used as such to benchmark third-party tools or any other experiments. We provide benchmark of some tools bellow.

Compatibility types

A set of other materials is provided to help with using the corpus. First, a table with API incompatibility results may be generated. The generation is invoked simply by typing:

./compatibility.sh

This script tries to commpile and run the client with both library versions and generates a CSV file with results. The file lists one-by-one each API change a informs if the change is source or binary compatible.

Example showing unboxing of a constant and access modifier change, where "1" means compatible while "0" incompatible:

Change Source Binary
dataTypeIfazeConstantUnboxing 1 0
accessModifierClazzAccessDecrease 0 0

Benchmark

Third party tools may be benchmarked. Run:

./benchmark.sh

It will invoke tested tools that are fed with the corpus data and their ability to discover API changes is checked. The results are stored in benchmark.csv table, where "1" means that a change was detected while "0" means that it was not.

The set of tested tools may be extended. Just edit the script tools/run.sh and add lines invoking the tool. Make sure the output of the tool is stored in directory tools/.reports/ in a textual form. The benchamrk script can then grap the report and parse results. Note that a detected API change is obtained simply by string matching.

Similarly, the set of test data may be extended simply by adding new changes to the src dirs. The data shuold only follow the naming pattern already used.

Tested Tools

Tools included in th benchmark:

Results

clirr jacc japicc japiChecker japicmp japitool jour revapi sigtest
Access Modifiers 100.00% 100.00% 83.33% 100.00% 100.00% 100.00% 83.33% 83.33% 100.00%
Data Types 100.00% 100.00% 89.36% 100.00% 100.00% 100.00% 100.00% 95.74% 100.00%
Exceptions 0.00% 0.00% 100.00% 100.00% 100.00% 100.00% 100.00% 71.43% 100.00%
Generics 0.00% 33.33% 5.88% 0.00% 0.00% 100.00% 17.65% 100.00% 100.00%
Inheritance 71.43% 100.00% 71.43% 85.71% 100.00% 100.00% 100.00% 42.86% 100.00%
Members 100.00% 100.00% 84.21% 89.47% 100.00% 100.00% 84.21% 42.11% 100.00%
Other Modifiers 61.54% 84.62% 84.62% 53.85% 84.62% 69.23% 76.92% 61.54% 84.62%
Others 100.00% 100.00% 75.00% 100.00% 100.00% 100.00% 100.00% 50.00% 100.00%
57.79% 72.08% 59.74% 61.04% 65.58% 97.40% 68.18% 82.47% 98.70%

About

This corpus contains examples of "all" possible syntactic API changes in Java.


Languages

Language:TeX 76.9%Language:Java 22.8%Language:Shell 0.3%