Last revised $Date: 2010/03/05 15:53:26 $
This plan is under continuous refinement. Please send comments about this plan to the firstname.lastname@example.org developer mailing list.
Note: This plan depends on the Platform Text Plan.
This section lists the goals for Eclipse 3.6 for the JDT Text and the JDT UI component as listed on the
Eclipse Project 3.6 Draft Plan.
 Scaling Up.
Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.
 Design for Extensibility.
Provide APIs for clients where needed.
 Ease of Use.
Make sure we run on the e4 compatibility layer and deliver new productivity features like TBD.
 Platform Support.
Add support for Java 7 and make sure we run on Windows 7.
 Technology Trends.
Add support for JUnit 4.7.
This section lists the possible work items for Eclipse 3.6 for the JDT Text and the JDT UI component
with the [corresponding theme].
Some of those items have a higher priority than others.
[> 3.6] Java 7 
Work for JSR308 which is publicly available is in progress in JDT Core. For the JSR292, JSR294 and project Coin we need to wait for publicly available specifications.
This probably means that Java 7 support won't be completely done for the 3.6 release. We might be able to get all we need in time for 3.6.1.
Note: In order to align our schedule with the delayed official Java 7 appearance and due to lack of publicly available
specifications (including lack of a Java 7 JSR), we have decided to move the development work to a separate branch and decouple it from the
3.6 release. In that branch we will continue to develop the Java 7 features as they become publicly accessible. We will deliver separate
updates for the official builds in order to provide early access to Java 7 features.
Windows 7 Support 
- test pass on Windows 7 Dani: 1w
- fix bugs that arise during test pass Dani: 1w
Adopt New Platform Features 
- make sure that we run on the e4 compatibility layer 2w
- test our bundles against it
- help to investigate and fix bugs in the compatibility layer
- provide a way for RefactoringWizardOpenOperation/RefactoringWizard to use a specified IRunnableContext (bug 283427) Markus
- provide container name for JUnit container (bug 161566) Markus
- new refactoring: move type to new file (bug 43277) Raksha: 3d
- new refactoring: convert instance method to static (bug 118032) Raksha: 2w
- decide on strategy to handle visibility errors after refactorings (and implement it correctly): Markus: 2w
- Increase visibility (with info/warning message)?
- add delegation if possible (with info/warning message)?
- offer possibility to "fix" warning on error page?
- 'Open Implementation' should also be available as command Raksha: 2d
- Allow to export all clean up and formatter profiles from preference page (bug 48966) Raksha: 2d
- provide link to clean up in enhanced problem hover (bug 218595) Raksha: 2w
- [>3.6] provide a trim to show number of error/warnings1w
- needs to be discussed with UI team first
→ this would bind too much resources from Platform UI and hence not for 3.6
- BiDi support for input fields/combos (related bugs, depends on SWT bug 230854) 6w
Java Search 
- [>3.6] search for text in attached source (bug 247503, depends on JDT Core bug 199994)
→ will be solved via text search participant support (bug 23341)
→ JDT Core tried to support to find constant references in .class files with attached source (bug 12044) but deferred this from 3.5
Call Hierarchy 
- allow to remove nodes from view (bug 41702) Raksha: 2d
Type Hierarchy 
- compute hierarchy in background (bug 30881) Raksha: 3d
- update JUnit 4 to 4.7 (bug 272418, CQ 3480) Markus: 1d
- separate UI from non-UI code (bug 278844) external contribution + Markus: 1d
- help to make JUnit 4 available as 'org.junit' bundle in Orbit (bug 186369 and bug 153429)
Content Assist 
- context information: show parameters should show parameters for all overloaded methods (bug 58719) Dani: 2d
- fix constructor completion bugs Dani: 3d
- indicate match in proposal list (similar to Ctrl+3)
Code Visualization 
- show horizontal line between methods (bug 13672) Raksha or Deepak: 1w
- visualize code nesting (bug 69455) Raksha or Prakash: 2w
→ could be implemented as semantic highlighting
- [misc] draw vertical lines in control flow statements (bug 84878)
Quick views 
- allow to open quick views from any Java element from any view (e.g. from the Package Explorer or Outline view) (bug 285411) Raksha or Prakash: 2d
Javadoc view and sticky Javadoc hover 
- show Java annotations (bug 236850) Markus: 2d
Performance And Memory Consumption 
- constantly watch performance test results and act when red
- continue to provide new tests
- adopt NodeFinder API (bug 250944) Markus: 1d
- add hyperlinking for the @inheritDoc tag Raksha: 2d
- structured selection should support brackets (bug 86835) Markus
- 3.5.x maintenance work 2w
- look at bugs with patches and review those
Cross Team Issues
This section contains cross team issues that have to be clarified. The
concrete outcome affects the plan items listed above.
- bug 230854 needs to be fixed in order to provide BiDi support for input fields/combos
- Platform Compare
- Platform UI
- JDT Core (3.6 plan)
- Java 7 features; detailed bugs TBD
- JDT Debug