Project Plan For Eclipse Web Tools Platform Project, version Helios


The Web Tool Platform (WTP) project provides extensible frameworks and exemplary tools to build Web and Java EE applications. This document describes the features and the API set for the Helios release.

Release Deliverables

There will be SDK and non-SDK versions of each of the main deliverables:

  • XML IDE (including XSL, XSD, etc)
  • JSDT (Javascript only)
  • Web Development (no Java technologies)
  • Java EE Development
  • EPP Packaging project: The Eclipse IDE for JavaScript Developers
  • EPP Packaging project: The Eclipse IDE for Java EE Developers

Table of Contents

Release Milestones

WTP Milestones follow the Eclipse release milestones by an offset of 2 as set by the Helios release schedule. For details, see the WTP 3.2 ramp down plan, Ramp down plan for WTP 3.2.

Note: The following are preliminary dates subject to change.


M1 milestone


M2 milestone. Initial WTP 3.2 plans for Helios due on 10/2.


M3 milestone.


M4 milestone.


M5 milestone


M6 milestone.Feature complete, API and UI Freeze


M7 milestone. PMC review starts


RC1 milestone.PMC approval required, 1 vote required


RC2 milestone.PMC approval required, 2 votes required


RC3 milestone.Document Freeze. PMC approval required, 3 votes required


RC4 milestone.Only stop-ship defects, PMC approval required, 3 vote required

Final Build6/11/2010

Final Build.



Table of Contents

Target Environments

WTP will support the platforms certified by the Eclipse Platform project. For a list of platforms supported in Helios, see Eclipse Target Operating Environments



Internationalization and Localization will be supported.

  • Internationalization (I18N)

    Each project should be able to work in an international environment, including support for operating in different locales and processing/displaying international data (dates, strings, etc.).

  • Localization

    Each project should provide an environment that supports the localization of the technology (i.e. translation). This includes, but is not limited to, ensuring that strings are externalized for easy translation.

  • Where possible, projects should use an open and transparent process to create, maintain and deliver language packs translated into multiple languages in a timely manner. The primary languages to consider are: English, Simplified Chinese, Traditional Chinese, Japanese, French, German, Spanish.

Table of Contents

Compatibility with Previous Releases

Table of Contents

Themes and Priorities

See the following sub-project plans for details

Sub-Project Plans:

Table of Contents


Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"