<?xml version="1.0" ?>
<!-- This file was exported from BibSonomy, http://www.bibsonomy.org -->

<bibliography>

<biblioentry xreflabel="paper:omori:2008" id="paper:omori:2008">
   <authorgroup>
       <author><firstname>Omori&#44;</firstname><surname>Takayuki</surname></author>
       <author><firstname>Maruyama&#44;</firstname><surname>Katsuhisa</surname></author> 
   </authorgroup>
<citetitle pubwork="article">A Change&#45;Aware Development Environment by Recording Editing Operations of Source Code</citetitle>

   <publisher>
      <publishername>ACM</publishername>
   </publisher>


   <artpagenums>31&#x2013;34</artpagenums> 
   <pubdate>2008</pubdate>  
   <abstract>
      <para>Understanding a program and its evolution is not satis&#64257;ed only by looking at a current snapshot of its source code. Thus&#44; a developer often examines a sequence of its snapshots stored in repositories of versioning systems&#44; and identi&#64257;es differences between two successive snapshots. Unfortunately&#44; 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&#45;in&#44; which is called OperationRecorder. The experimental results with a small&#45;scale program substantiate that it has a practical use from the viewpoint of its performance.
      </para>
   </abstract>
</biblioentry>
<biblioentry xreflabel="myee" id="myee">
   <authorgroup>
       <author><firstname>Aniszczyk&#44;</firstname><surname>Chris</surname></author>
       <author><firstname>Crosby&#44;</firstname><surname>Phil</surname></author> 
   </authorgroup>
<citetitle pubwork="article">Manage your Eclipse environment</citetitle>





   <pubdate>2006</pubdate>  
   <abstract>
      <para>The continuing growth of Eclipse means that there will always be an increase in the number of projects and plug&#45;ins to manage. As a developer&#44; this management process can be frustrating when staying up to date with the latest Eclipse builds. As a new user&#44; the concept of projects&#44; plug&#45;ins&#44; workspaces&#44; and installations may seem daunting at first. This article aims to show some best practices for managing your Eclipse environment.
      </para>
   </abstract>
</biblioentry>
</bibliography>

