Eclipse Web Tools Platform Project 3.3.0

Release Date
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
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.

Target Environments

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

.

Themes

Enhance support for Java EE 6

WTP should be up-to-date with supporting the latest Java EE specification level. WTP should enhance the tooling support for Java EE 6.

Eclipse 4.1

WTP will support 4.1 as a secondary platform (while 3.7 will be primary platform). This means we will occasionally compile against it, or use API Tools, to make sure we are in API compliance with the 4.x compatibility layer. Committers and community will occasionally, but informally test with it. It will not be a fully tested platform. If the bug occurs only with 4.1, we will accept bugs as valid and prioritize along with bugs against 3.7 based builds. but will request submitters to try and reproduce on 3.7 first. We will not exploit anything specific to the Eclipse 4.1 Platform.