Analyzing the Eclipse API Usage: Putting the Developer in the Loop

Simple item page
dc.contributor.authorBusinge, John
dc.contributor.authorSerebrenik, Alexander
dc.contributor.authorvan den Brand, Mark
dc.date.accessioned2023-02-05T10:55:19Z
dc.date.available2023-02-05T10:55:19Z
dc.date.issued2013
dc.description.abstractEclipse guidelines distinguish between two types of interfaces provided to third-party developers, i.e., APIs and non-APIs. APIs are stable and supported, while non-APIs are unstable, unsupported and discouraged as they are subject to arbitrary change or removal without notice. In our previous work, we found that despite the discouragement of Eclipse, the use of non-APIs in Eclipse third-party plug-ins (ETPs) is not uncommon. Furthermore, we found that these non-APIs are the main cause of ETP incompatibilities in forthcoming releases of the Eclipse. In the current work we conducted a survey aiming at understanding why do the ETP developers use non-APIs. We have observed that developers with a level of education of up to master degree have a tendency not to read product manuals/ guidelines. Furthermore, while for less experienced developers instability of the non-APIs overshadows their benefits, more experienced developers prefer to enjoy the benefits of non-APIs despite the instability problem. Finally, we have observed that there are no significant differences between Open Source and commercial Eclipse products in terms of awareness of Eclipse guidelines and interfaces, Eclipse product size and updating of Eclipse product in the new SDK releases.en_US
dc.identifier.citationBusinge, J., Serebrenik, A., & van den Brand, M. (2013, March). Analyzing the Eclipse API usage: Putting the developer in the loop. In 2013 17th European Conference on Software Maintenance and Reengineering (pp. 37-46). IEEE.en_US
dc.identifier.urihttps://ieeexplore.ieee.org/abstract/document/6498453/
dc.identifier.urihttps://nru.uncst.go.ug/handle/123456789/7540
dc.language.isoenen_US
dc.publisherIEEEen_US
dc.subjectEclipseen_US
dc.subjectAPIsen_US
dc.subjectnon-APIsen_US
dc.subjectSurveyen_US
dc.subjectDevelopersen_US
dc.titleAnalyzing the Eclipse API Usage: Putting the Developer in the Loopen_US
dc.typeOtheren_US
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
Analyzing the Eclipse API Usage.pdf
Size:
191.84 KB
Format:
Adobe Portable Document Format
Description:
Proceedings
Download
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.71 KB
Format:
Item-specific license agreed upon to submission
Description:
Download
Collections
Engineering and Technology