Project Plan For Eclipse Web Tools Platform Project, version 3.1

Introduction

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 Galileo 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 (non Java)
  • JEE Development
  • EPP Packaging project: The Eclipse IDE for JEE Developers

Table of Contents

Release Milestones

WTP Milestones follow the Eclipse release milestones by an offset of 2 as set by the Galileo release schedule.

M18/22/2008

M1 milestone

M209/26/2008

M2 milestone.

M311/07/2008

M3 milestone

M412/19/2008

M4 milestone

M52/06/2009

M5 milestone

M63/20/2009

M6 milestone.Feature complete, API and UI Freeze

M75/08/2009

M7 milestone. PMC review starts

RC15/22/2009

RC1 milestone.PMC approval required, 1 vote required

RC25/29/2009

RC2 milestone.PMC approval required, 2 votes required

RC36/05/2009

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

RC46/12/2009

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

RC56/19/2009

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

GA6/24/2009

GA

Table of Contents

Target Environments

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

.

Internationalization

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

Appendix

Table of Contents

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