Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CDT/Archive/planning/Juno"

< CDT‎ | Archive‎ | planning
(Debug)
(Build)
Line 2: Line 2:
  
 
=== Build ===
 
=== Build ===
# Scanner Discovery redesign [https://bugs.eclipse.org/bugs/show_bug.cgi?id=290631 bug 290631]. Requires API changes in cdt.core.
+
# Scanner Discovery redesign [https://bugs.eclipse.org/bugs/show_bug.cgi?id=290631 bug 290631].
  
 
=== Debug ===
 
=== Debug ===

Revision as of 11:44, 7 February 2012

This is the plan for the CDT release for Eclipse Juno. We are not sure yet whether this will be release 8.1 or 9.0. It depends on whether we can get away without changing API.

Build

  1. Scanner Discovery redesign bug 290631.

Debug

  1. Breakpoint improvements
    • bug 360280 - Reposition breakpoints when planted on invalid line
    • bug 360291 - Allow user to edit line breakpoint file in properties dialog
    • bug 360295 - Customize property dialog for editing breakpoints
    • bug 360289 - Allow address breakpoint to be set on arbitrary expression
    • bug 360588 - Allow user to edit all its properties prior to creating the breakpoint
  2. Visualizer View
  3. OS Awareness
  4. Grouping of debug elements
    • bug 240208 - A single VMNode should represent all execution levels
    • bug 336876 - Grouping of Execution Elements for DSF debugger feature
  5. Global breakpoints support
  6. Better tracepoint visualization support (based on planned GDB feature)

Indexer

  1. Add support for headers included in different variants - bug 197989

Refactoring

  1. Move all refactorings to the new framework using shared ASTs
  2. Auto-format code modified by refactoring

Please add your items here.

Back to the top