This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
2013 17th European Conference on Software Maintenance and Reengineering
Analyzing the Eclipse API Usage: Putting the Developer in the Loop
Genova, Italy Italy
March 05-March 08
ISBN: 978-1-4673-5833-0
Eclipse 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.
Index Terms:
Developers,Eclipse,APIs,non-APIs,Survey
Citation:
John Businge, Alexander Serebrenik, Mark van den Brand, "Analyzing the Eclipse API Usage: Putting the Developer in the Loop," csmr, pp.37-46, 2013 17th European Conference on Software Maintenance and Reengineering, 2013
Usage of this product signifies your acceptance of the Terms of Use.