Show simple item record

dc.contributor.authorBusinge, John
dc.contributor.authorSerebrenik, Alexander
dc.contributor.authorBrand, Mark van den
dc.date.accessioned2021-06-02T06:43:35Z
dc.date.available2021-06-02T06:43:35Z
dc.date.issued2012
dc.identifier.citationBusinge, 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.urihttp://ir.must.ac.ug/xmlui/handle/123456789/896
dc.description.abstractToday 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 releaseen_US
dc.language.isoen_USen_US
dc.publisherInternational Conference on Software Maintenance (ICSM)en_US
dc.subjectThird-party plug-insen_US
dc.subjectAPIs; non-APIsen_US
dc.titleSurvival of Eclipse Third-party Plug-insen_US
dc.typeArticleen_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record