Appendix B. Changes in Version 2.0

The sections below document features and compatibility changes introduced in Red Hat Developer Toolset 2.0.

B.1. Changes in Eclipse

Red Hat Developer Toolset 2.0 is distributed with Eclipse 4.3 and a wide selection of plug-ins from the Eclipse Foundation's 2013 Eclipse 4.3 “Kepler” release, and provides a number of bug fixes and feature enhancements over the Red Hat Enterprise Linux system version.
Below is a comprehensive list of new features and compatibility changes in this release. For details on how to use these new features, see the built-in Eclipse documentation.

B.1.1. Changes Since Red Hat Enterprise Linux 6.4

The following features have been added since the release of the Eclipse Platform and native plug-ins included in Red Hat Enterprise Linux 6.4:
  • The Eclipse Platform has been updated from version 3.6 to 4.3. This new major release features a more flexible user interface based on Eclipse Modeling Framework (EMF), CSS-based themes, dependency injection, and more.
  • The Eclipse C/C++ Development Toolkit (CDT) has been updated from version 7.0 to 8.2. This new major release includes:
    • a greatly enhanced indexer, both in terms of capabilities and speed;
    • improved GNU Debugger integration;
    • support for GNU Debugger's pretty-printing;
    • multi-process debugging;
    • project-less debugging;
    • enhanced refactoring;
    • code-checking capabilities;
    • an improved and more polished user interface.
  • Mylyn, a set of task and application life cycle management plug-ins, has been updated from version 3.4 to 3.9. This update includes:
    • an enhanced task-focused interface and task editing;
    • a new Jenkins/Hudson connector;
    • enhanced Bugzilla and Trac connectors;
    • EPUB authoring tools.
  • A new EGit plug-in has been added. This plug-in includes an Eclipse Team provider based on JGit, a Git implementation written entirely in Java, and adds support for the Git revision control system to the Eclipse user interface by introducing the History and Synchronize views, Compare and Quick Diff menu items, and various wizards to make it easier for developers to use this plug-in.
  • New GCov integration has been added to allow the user to visualize GCov output in both summarized form and in file editors. As well, graphing capabilities for the data have been added.
  • New GProf integration has been added to allow the user to view profiling information such as execution time and call graphs. As well, graphing capabilities for the data have been added.
  • A new SystemTap integration plug-in has been added. This plug-in includes:
    • an editor for the .stp files with the autocomplete feature;
    • the Probe view with a list of probes that are available on the system;
    • the Function view with a list of functions that are available on the system and can be used in .stp scripts.
    As well, this plug-in includes integration for running SystemTap scripts and viewing the results in a textual, tabular, and graphical manner. Note that the result sets are updated in a near-runtime way, which allows the user to use this plug-in for longer-running monitoring tasks.
  • New kernel perf tool integration has been added. This plug-in uses the performance counters subsystem of the Linux kernel to profile applications, makes it easier to analyze the results by hyperlinking to the sources in the workspace projects, simplifies the perf tool configuration by selecting the counters to be used, and allows the user to run this tool remotely.
  • A unified profiling launcher has been added to provide a single method to launch profiling. It allows the user to select a profiling category (Memory, Timing, or Coverage) and back ends for this category (such as OProfile, perf, or GProf for Timing).
  • The C/C++ documentation plug-in has been enhanced to recognize and use gtk-doc generated documentation and to display it in the Eclipse Help Center.
  • The OProfile plug-in has been enhanced to support root privilege authentication through polkit. This feature is configured automatically.
  • The Valgrind plug-in now supports the Helgrind tool, which can be used to detect synchronization problems such as race conditions, deadlocks caused by incorrect locking order, or misuse of the POSIX pthreads API. When a problem is detected, the plug-in displays error markers on the corresponding lines in the source code.