| dc.contributor.author | Businge, John | |
| dc.contributor.author | Serebrenik, Alexander | |
| dc.contributor.author | Brand, Mark van den | |
| dc.date.accessioned | 2021-06-02T06:43:35Z | |
| dc.date.available | 2021-06-02T06:43:35Z | |
| dc.date.issued | 2012 | |
| dc.identifier.citation | Businge, J., Serebrenik, A., & van den Brand, M. (2012, September). Survival of Eclipse third-party plug-ins. In 2012 28th IEEE International Conference on Software Maintenance (ICSM) (pp. 368-377). IEEE. | en_US |
| dc.identifier.uri | http://ir.must.ac.ug/xmlui/handle/123456789/896 | |
| dc.description.abstract | Today numerous software systems are being developed on top of frameworks. In this study, we analyzed the survival of 467 Eclipse third-party plug-ins altogether having 1,447 versions. We classify these plug-ins into two categories: those that depend on only stable and supported Eclipse APIs and those that depend on at least one of the potentially unstable, discouraged and unsupported Eclipse non-APIs. Comparing the two categories of plug-ins, we observed that the plug-ins depending solely on APIs have a very high source compatibility success rate compared to those that depend on at least one of the non-APIs. However, we have also observed that recently released plug-ins that depend on non-APIs also have a very high forward source compatibility success rate. This high source compatibility success rate is due to the dependency structure of these plug-ins: recently released plug-ins that depend on non-A PIs predominantly depend on old Eclipse non APIs rather than on newly introduced ones. Finally, we showed that the majority of plug-ins hosted on Source Forge do not evolve beyond the first year of release | en_US |
| dc.language.iso | en_US | en_US |
| dc.publisher | International Conference on Software Maintenance (ICSM) | en_US |
| dc.subject | Third-party plug-ins | en_US |
| dc.subject | APIs; non-APIs | en_US |
| dc.title | Survival of Eclipse Third-party Plug-ins | en_US |
| dc.type | Article | en_US |
