Eclipse Technology eXchange 

Abstract: Most open source software development projects include an open bug repository---one to which users of the software can gain full access---that is used to report and track problems with, and potential enhancements to, the software system. There are several potential advantages to the use of an open bug repository: more problems with the system might be identified because of the relative ease of reporting bugs, more problems might be fixed because more developers might engage in problem solving, and developers and users can engage in focused conversations about the bugs, allowing users input into the direction of the system. However, there are also some potential disadvantages such as the possibility that developers must process irrelevant bugs that reduce their productivity. Despite the rise in use of open bug repositories, there is little data about what is stored inside these repositories and how they are used. In this paper, we provide an initial characterization of two open bug repositories from the Eclipse and Firefox projects, describe the duplicate bug and bug triage problems that arise with these open bug repositories, and discuss how we are applying machine learning technology to help automate these processes.

Abstract: Collaboration is an integral part of software development, occurring through tools inside and outside the IDE. This paper presents an overview of the Jazz project, which seeks to integrate collaborative capabilities into the Eclipse IDE, enabling small teams of software developers to work together more productively.

Abstract: The information in bug reports influences the speed at which bugs are fixed. However, bug reports differ in their quality of information. We conducted a survey among ECLIPSE developers to determine the information in reports that they widely used and the problems frequently encountered. Our results show that steps to reproduce and stack traces are most sought after by developers, while inaccurate steps to reproduce and incomplete information pose the largest hurdles. Surprisingly, developers are indifferent to bug duplicates. Such insight is useful to design new bug tracking tools that guide reporters at providing more helpful information. We also present a prototype of a quality-meter tool that measures the quality of bug reports by scanning its content.

Abstract: We introduce ConcernMapper, an Eclipse plug-in for experimenting with techniques for advanced separation of concerns. ConcernMapper supports development and maintenance tasks involving scattered concerns by allowing developers to organize and view the code of a project in terms of high-level abstractions called concerns. ConcernMapper is also designed as an extensible platform intended to provide a simple way to store and query concern models created through a variety of approaches. This paper describes the user interface and internal architecture of ConcernMapper, and demonstrates how to write extensions for it.