Catchup! capturing and replaying refactorings to support API evolution

Henkel, Johannes; Diwan, Amer

doi:10.1109/icse.2005.1553570

Cited by 132 publications

(161 citation statements)

References 6 publications

Supporting

Mentioning

161

Contrasting

Order By: Relevance

“…Chow and Notkin [39] present an approach where the API developers annotate changed methods with replacement rules that will be used to update client systems. Henkel and Diwan [40] propose CatchUp!, a tool using an IDE to capture and replay refactorings related to the API evolution. Dig et al [41] propose a refactoring-aware version control system for the same purposes.…”

Section: Threats To Validitymentioning

confidence: 99%

On the Reaction to Deprecation of 25,357 Clients of 4+1 Popular Java APIs

Sawant

Robbes

Bacchelli

2016

2016 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

Abstract-Application Programming Interfaces (APIs) are a tremendous resource-that is, when they are stable. Several studies have shown that this is unfortunately not the case. Of those, a large-scale study of API changes in the Pharo Smalltalk ecosystem documented several findings about API deprecations and their impact on API clients.We conduct a partial replication of this study, considering more than 25,000 clients of five popular Java APIs on GitHub. This work addresses several shortcomings of the previous study, namely: a study of several distinct API clients in a popular, statically-typed language, with more accurate version information. We compare and contrast our findings with the previous study and highlight new ones, particularly on the API client update practices and the startling similarities between reaction behavior in Smalltalk and Java.

show abstract

Section: Threats To Validitymentioning

confidence: 99%

On the Reaction to Deprecation of 25,357 Clients of 4+1 Popular Java APIs

Sawant

Robbes

Bacchelli

2016

2016 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

show abstract

“…Chow and Notkin (1996) present an approach where the API developers annotate changed methods with replacement rules that will be used to update client systems. Henkel and Diwan (2005) propose CatchUp!, a tool using an IDE to capture and replay refactorings related to the API evolution. Dig et al (2007) propose a refactoring-aware version control system for the same purposes.…”

Section: Supporting Api Evolutionmentioning

confidence: 99%

On the reaction to deprecation of clients of 4 + 1 popular Java APIs and the JDK

2017

View full text Add to dashboard Cite

Application Programming Interfaces (APIs) are a tremendous resource-that is, when they are stable. Several studies have shown that this is unfortunately not the case. Of those, a large-scale study of API changes in the Pharo Smalltalk ecosystem documented several findings about API deprecations and their impact on API clients. We extend this study, by analyzing clients of both popular third-party Java APIs and the JDK API. This results in a dataset consisting of more than 25,000 clients of five popular Java APIs on GitHub, and 60 clients of the JDK API from Maven Central. This work addresses several shortcomings of the previous study, namely: a study of several distinct API clients in a popular, statically-typed language, with more accurate version information. We compare and contrast our findings with the previous study and highlight new ones, particularly on the API client update practices and the startling similarities between reaction behavior in Smalltalk and Java. We make a comparison between reaction behavior for third-party APIs and JDK APIs, given that language APIs are a peculiar case in terms of wide-spread usage, documentation, and support from IDEs. Furthermore, we investigate the connection between reaction patterns of a client and the deprecation policy adopted by the API used.

show abstract

“…Record-and-replay of refactorings was demonstrated in CatchUp [HD05] and JBuilder2005 [Bor] and recently incorporated in Eclipse 3.2 Milestone 4 [Ecl]. As component developers refactor their code, the refactoring engine creates a log of refactorings.…”

Section: Introductionmentioning

confidence: 99%

Automated Detection of Refactorings in Evolving Components

Dig

Comertoglu

Marinov

et al. 2006

ECOOP 2006 – Object-Oriented Programming

187

165

View full text Add to dashboard Cite

Abstract.One of the costs of reusing software components is updating applications to use the new version of the components. Updating an application can be error-prone, tedious, and disruptive of the development process. Our previous study showed that more than 80% of the disruptive changes in five different components were caused by refactorings. If the refactorings that happened between two versions of a component could be automatically detected, a refactoring tool could replay them on applications. We present an algorithm that detects refactorings performed during component evolution. Our algorithm uses a combination of a fast syntactic analysis to detect refactoring candidates and a more expensive semantic analysis to refine the results. The experiments on components ranging from 17 KLOC to 352 KLOC show that our algorithm detects refactorings in real-world components with accuracy over 85%.

show abstract

Catchup! capturing and replaying refactorings to support API evolution

Cited by 132 publications

References 6 publications

On the Reaction to Deprecation of 25,357 Clients of 4+1 Popular Java APIs

On the Reaction to Deprecation of 25,357 Clients of 4+1 Popular Java APIs

On the reaction to deprecation of clients of 4 + 1 popular Java APIs and the JDK

Automated Detection of Refactorings in Evolving Components

Contact Info

Product

Resources

About