Evaluating the Impact of Third-Party Library Reuse in Java Projects: An Empirical Study

Update, we have added the following:
- `dataset.ipynb`: Computes all the dataset used for this study. The user needs to use a call graph generator like OPAL/WALA.

- `loc.ipynb`: Computes a dataset for LOC information given a call graph dataset

- `called-reuse.ipynb`: Computing a dataset for all called functions and LOC in third-party libraries

- `megamorphic.ipynb`: Empirically decide the megamorphic call sites. 

This part of the submission related to the paper "Evaluating the Impact of Third-Party Library Reuse in Java Projects: An Empirical Study". Here is a table of contents:

• `census.csv`: extracted data from the Census-II
• `releases_all.csv`: all releases available from Maven Coordinates in Census-II
• `releases_jar.csv`: dataset of all releases with a POM and JAR file
• `releases_jar_6_months.csv`: releases selected when studiying the 6-month interval
• `releases_jar_6_months.csv`: releases selected when comparing consecutive versions per artefactid and groupid
• `loc_composition.csv`: data on the ratio of insourced and outsourced code in project releases
• `loc_desc_without_lambdas.csv`: mined data on LOC information and class information.
• `loc_reuse_lower_bound.csv`: data on the ratio of reused LOC and functions of outsourced code, lower-bound
• `loc_reuse_upper_bound.csv`:  data on the ratio of reused LOC and functions of outsourced code, upper-bound