CatchUp! Capturing and replaying refactorings to support API evolution

By Johannes Henkel, Amer Diwan. Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005., 2005

309 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Smart Contract Development: Challenges and Opportunities (2021, background): “Studies are needed to explore if existing research solutions [57], [63] work well for Solidity API and if not, novels solutions are needed.”
Accurate and Efficient Refactoring Detection in Commit History (2018, methodology): “Other researchers used refactoring detection to empirically study [4, 6, 7, 45, 61, 63, 73] software evolution, and to support other software engineering tasks, such as library adaptation [5, 18, 40, 79], software merging [21], code completion [27, 31], and code review [1, 33, 34].”
UMLDiff: an algorithm for object-oriented design differencing (2005, methodology): “CatchUp [9] is an attempt to relieve this burden by recording the refactorings, such as method renamings, made by the library developers within an IDE, such as Eclipse, and then replaying them by the application developers on the library client code to keep it updated.”
Divide-and-Conquer Approach for Multi-phase Statistical Migration for Source Code (T) (2015, background): “There are approaches to support adaptation to client code as libraries evolve [6], [7], [14].”