Analyzing the evolution of eclipse plugins

Authors:
Michel Wermelinger;Yijun Yu
Affiliations:
The Open University, Milton Keynes, United Kingdom;The Open University, Milton Keynes, United Kingdom
Venue:
Proceedings of the 2008 international working conference on Mining software repositories
Year:
2008

Citing 1
Cited 5

Efficient Relational Calculation for Software Analysis

IEEE Transactions on Software Engineering

Evaluating Process Quality Based on Change Request Data --- An Empirical Study of the Eclipse Project

IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
Rigi-An environment for software reverse engineering, exploration, visualization, and redocumentation

Science of Computer Programming
An empirical study of the evolution of Eclipse third-party plug-ins

Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE)
Some issues in the 'archaeology' of software evolution

GTTSE'09 Proceedings of the 3rd international summer school conference on Generative and transformational techniques in software engineering III
Perpetual development: A model of the Linux kernel life cycle

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Eclipse is a good example of a modern component-based complex system that is designed for long-term evolution, due to its architecture of reusable and extensible components. This paper presents our preliminary results about the evolution of Eclipse's architecture, based on a lightweight and scalable analysis of the metadata in Eclipse's sources. We find that the development of Eclipse follows a systematic process: most architectural changes take place in milestones, and maintenance releases only make exceptional changes to component dependencies. We also found a stable architectural core that remains since the first release.