Show simple item record

dc.contributor.authorSawant A
dc.contributor.authorRobbes R
dc.contributor.authorBacchelli A
dc.date.accessioned2018-10-19T12:59:02Z
dc.date.available2018-10-19T12:59:02Z
dc.date.issued2018
dc.identifier.issn1382-3256
dc.identifier.urihttp://dx.doi.org/10.1007/s10664-017-9554-9
dc.identifier.urihttp://hdl.handle.net/10863/6603
dc.description.abstractApplication 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. © 2017, The Author(s).en_US
dc.language.isoenen_US
dc.rights
dc.titleOn the reaction to deprecation of clients of 4 + 1 popular Java APIs and the JDKen_US
dc.typeArticleen_US
dc.date.updated2018-10-05T16:15:32Z
dc.language.isiEN-GB
dc.journal.titleEmpirical Software Engineering
dc.description.fulltextreserveden_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record