-
- Michele Tufano
- The College of William and Mary Williamsburg VA USA
-
- Fabio Palomba
- University of Salerno Fisciano Italy
-
- Gabriele Bavota
- Università della Svizzera italiana (USI) Lugano Switzerland
-
- Massimiliano Di Penta
- University of Sannio Benevento Italy
-
- Rocco Oliveto
- University of Molise Campobasso Italy
-
- Andrea De Lucia
- University of Salerno Fisciano Italy
-
- Denys Poshyvanyk
- The College of William and Mary Williamsburg VA USA
説明
<jats:p>A broken snapshot represents a snapshot from a project's change history that cannot be compiled. Broken snapshots can have significant implications for researchers, as they could hinder any analysis of the past project history that requires code to be compiled. Noticeably, while some broken snapshots may be observable in change history repositories (e.g., no longer available dependencies), some of them may not necessarily happen during the actual development. In this paper, we systematically study the compilability of broken snapshots in 219 395 snapshots belonging to 100 Java projects from the Apache Software Foundation, all relying on Maven as an automated build tool. We investigated broken snapshots from 2 different perspectives: (1) how frequently they happen and (2) likely causes behind them. The empirical results indicate that broken snapshots occur in most (96%) of the projects we studied and that they are mainly due to problems related to the resolution of dependencies. On average, only 38% of the change history of the analyzed systems is <jats:italic>currently</jats:italic> successfully compilable.</jats:p>
収録刊行物
-
- Journal of Software: Evolution and Process
-
Journal of Software: Evolution and Process 29 (4), 2016-12-20
Wiley
- Tweet
詳細情報 詳細情報について
-
- CRID
- 1360017677372184448
-
- DOI
- 10.1002/smr.1838
-
- ISSN
- 20477481
- 20477473
-
- データソース種別
-
- Crossref