Release Date
Deliverables
The PDT source code is contained in the org.eclipse.pdt.git repo and for this release is tagged R3_3. Service releases are planned which will have the tags R3_3_1 for SR-1.
The PDT provides it's own update site with all features included. For 3.3, this site is located at http://download.eclipse.org/tools/pdt/updates/3.3
Compatibility
API compatability is maintained with previous 3.x PDT releases. PDT 3.3 will run against 3.8 and newer Eclipse Platform releases.
Internationalization
PDT has all Strings externalized.
Target Environments
PDT targets all supported Eclipse enviornments.
Themes
Maintenance
Actively fix bugs reported by community in core areas, such as content assist, code editing, general GUI.
Work with community
Embrace community by working with active contributors, PDT extenders group, towards adding their contributions to PDT.
Library folders
We want to enable users to mark source folders as library folders. The files inside a library folder are not validated, but are still indexed, so context assist and search capabilities remain.
The main goal addressed is usability. In huge projects with lots of dependencies fetched with composer, there are lots of errors and warnings that clutter the Problems view. This makes it more difficult for the developer to focus on her own application code. Marking such folders (like "vendor") as library folders will filter all these problem markers. There is also a positive performance impact due to the less CPU time spent in parsing and validation.
Parser improvements
Reporting structural changes (like new class, rename method, new parameters etc..) to DLTK in PDT IBuildParticipant. Required for example to build JDT/JSDT like semantic analysis for PHP. Experimental ASTConverter (from compiler AST to DOM AST), similar to JDT. When finished, second parsed will be not required and overall performance in most cases should be improved.
This release is part of Luna