Eclipse Application Programming Interfaces:
| dc.contributor.author | Kawuma, Simon | |
| dc.contributor.author | Bamutura, David Sabiiti | |
| dc.contributor.author | Obbo, Aggrey | |
| dc.contributor.author | Mabirizi, Vicent | |
| dc.contributor.author | Kabarungi, Moreen | |
| dc.contributor.author | Nabaasa, Evarist | |
| dc.date.accessioned | 2025-09-30T16:10:12Z | |
| dc.date.available | 2025-09-30T16:10:12Z | |
| dc.date.issued | 2025 | |
| dc.description.abstract | Eclipse Framework provides stable public APIs and unstable internal APIs. However, there is no guarantee that these interfaces are well tested because several bugs are reportedby interface users on Bugzilla-based Eclipse project. Applications that use buggy APIs risk failing if bugs are not fixed. Bug fixation and resolution takes at least 3 years thus API users have to fix the bugs themselves or abandon that particular API. The study aimed at identifying bug free interfaces in the Eclipse Framework and recommend them to application developers. In this research study, we used both SonarQube and SpotBugs static analysis tools to carry out an empirical investigation on 28 major Eclipse releases to establish the existence of bug free interfaces. We provide a dataset of 218K and 303K bug-free public API and internal API respectively. There exist over $85.9%$ and $88.2%$ bug-free public APIs and internal APIs, respectively, in Eclipse releases. Furthermore, over 80.8% and 44.2% are major and malicious code vulnerability bugs respectively and the average bug remediation effort is 105 days. Results from this study can be used by both interface providers and users as a starting point to know tested interfaces and also estimate efforts needed to fix bugs and an online dataset of bug-free interface is available on Github for developer. | |
| dc.identifier.citation | Kawuma, S., Bamutura, D. S., Obbo, A., Mabirizi, V., Kabarungi, M., & Nabaasa, E. (2025). Eclipse Application Programming Interfaces: How Buggy Are They?. VFAST Transactions on Software Engineering, 13(2), 228-244. | |
| dc.identifier.issn | 2309-3978, | |
| dc.identifier.uri | http://hdl.handle.net/20.500.12493/2949 | |
| dc.language.iso | en | |
| dc.publisher | VFAST Transactions on Software Engineering | |
| dc.rights | Attribution-NonCommercial-NoDerivs 3.0 United States | en |
| dc.rights.uri | http://creativecommons.org/licenses/by-nc-nd/3.0/us/ | |
| dc.subject | Eclipse | |
| dc.subject | public APIs | |
| dc.subject | internal APIs | |
| dc.subject | Bugs | |
| dc.subject | Software Quality | |
| dc.subject | Evolution. | |
| dc.title | Eclipse Application Programming Interfaces: | |
| dc.title.alternative | How Buggy Are They? | |
| dc.type | Article |