Build code analysis with symbolic evaluation

TL;DR: This paper derives three repair strategies to automatically repair Maven builds that break due to dependency-related issues, namely Version Update, Delete Dependency, and Add Repository, and shows that BuildMedic can automatically repair 45 of these broken builds.

TL;DR: The prevalence of different build technologies and the relationship between build technology and build maintenance are understood by analyzing version histories in a corpus of 177,039 repositories spread across four software forges, three software ecosystems, and four large-scale projects.

TL;DR: A case study on unspecified dependencies in the make-based build systems of the glib, openldap, linux and qt open source projects is presented and it is found that unspecified dependencies are common.

TL;DR: A qualitative study on a set of five multilanguages open source software packages found that there are commonalities among build problems that can be systematically addressed, and one such finding is that multilanguage packages avoid certain build problems by supporting compilation-free extension.

TL;DR: This research is compared and discussed based on a number of different criteria: the refactoring activities that are supported, the specific techniques and formalisms that are used for supporting these activities, the types of software artifacts that are being refactored, the important issues that need to be taken into account when buildingRefactoring tool support, and the effect of refactors on the software process.

TL;DR: This paper shows that it is possible to circumvent this hindrance by applying a language independent and visual approach, i.e. a tool that requires no parsing, yet is able to detect a significant amount of code duplication.

TL;DR: This paper presents an approach for the automatic detection and visualization of code smells and discusses how this approach can be used in the design of a software inspection tool.

TL;DR: Differential symbolic execution (DSE) as discussed by the authors exploits the fact that program versions are largely similar to reduce cost and improve the quality of analysis results, and demonstrates its potential benefit through an exploratory study that considers version histories of two Java code bases.