Omori, T. & Maruyama, K.: A Change-Aware Development Environment by Recording Editing Operations of Source Code. MSR '08: Proceedings of the 2008 international workshop on Mining software repositories. New York, NY, USA: ACM, 2008, S. 31-34
Understanding a program and its evolution is not satisfied only by looking at a current snapshot of its source code. Thus, a developer often examines a sequence of its snapshots stored in repositories of versioning systems, and identifies differences between two successive snapshots. Unfortunately, such differences do not represent individual changes of the source code. This paper proposes a mechanism for recording all editing operations a developer has applied to source code on an integrated development environment. The paper also shows a running implementation of the mechanism built as an Eclipse plug-in, which is called OperationRecorder. The experimental results with a small-scale program substantiate that it has a practical use from the viewpoint of its performance.
@inproceedings{paper:omori:2008,
author = {Omori, Takayuki and Maruyama, Katsuhisa},
title = {A Change-Aware Development Environment by Recording Editing Operations of Source Code},
booktitle = {MSR '08: Proceedings of the 2008 international workshop on Mining software repositories},
publisher = {ACM},
address = {New York, NY, USA},
year = {2008},
pages = {31--34},
keywords = {code development diff eclipse paper plugin read:2008 recording source},
abstract = {Understanding a program and its evolution is not satisfied only by looking at a current snapshot of its source code. Thus, a developer often examines a sequence of its snapshots stored in repositories of versioning systems, and identifies differences between two successive snapshots. Unfortunately, such differences do not represent individual changes of the source code. This paper proposes a mechanism for recording all editing operations a developer has applied to source code on an integrated development environment. The paper also shows a running implementation of the mechanism built as an Eclipse plug-in, which is called OperationRecorder. The experimental results with a small-scale program substantiate that it has a practical use from the viewpoint of its performance.}
}
Aniszczyk, C. & Crosby, P.: Manage your Eclipse environment. (2006),
[Volltext]
The continuing growth of Eclipse means that there will always be an increase in the number of projects and plug-ins to manage. As a developer, this management process can be frustrating when staying up to date with the latest Eclipse builds. As a new user, the concept of projects, plug-ins, workspaces, and installations may seem daunting at first. This article aims to show some best practices for managing your Eclipse environment.
@article{myee,
author = {Aniszczyk, Chris and Crosby, Phil},
title = {Manage your Eclipse environment},
year = {2006},
url = {http://www-128.ibm.com/developerworks/opensource/library/os-ecl-manage/},
keywords = {article eclipse environment ibm manage read:2008},
abstract = {The continuing growth of Eclipse means that there will always be an increase in the number of projects and plug-ins to manage. As a developer, this management process can be frustrating when staying up to date with the latest Eclipse builds. As a new user, the concept of projects, plug-ins, workspaces, and installations may seem daunting at first. This article aims to show some best practices for managing your Eclipse environment.}
}