Project Plan For WTP Java EE Tools, version Kepler

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 in the Java EE Tools subproject for the Kepler release.

Release Deliverables

  • WTP non-SDK package
  • WTP SDK Package
  • WST non-SDK package
  • WST SDK Package
  • The Eclipse IDE for Java EE Developers package

Table of Contents

Target Environments

WTP will support the platforms certified by the c. For a list of platforms supported in WTP 3.5, 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

Themes and their priorities communicate the main objectives of the project and their importance. These will be prioritized based on the community feedback. New themes could be synthesized from the requirements submitted by the community.

Primarily the Java EE project will be focusing on maintenance issues, fixing bugs, upgrading dependencies, and providing small enhancements using the following themes.

The sections to follow defines the plan items in the Java EE Tools project. The plan items are grouped under the respective themes where applicable. Each plan item corresponds to a new feature, API or some apsects of the project that needs to be improved. A plan item has an entry in the Eclipse Bugzilla system that has a detailed description of the plan item. Not all plan items represent the same amount of work; some may be quite large, others, quite small. Although some plan items are for work that is more pressing than others, the plan items appear in no particular order. See the corresponding bugzilla items for up-to-date status information on ongoing work and planned delivery milestones.

Maven (m2e) integration

Features provided by WTP should be simple to use for users with widely-varying backgrounds and skill sets.

  • WTP will work towards integrating, and enabling the m2e-wtp specific project builders, classpath management, and UI.

  • Proposed

    • [API] Add the ability to specify the deployed archiveName for Jars/projects defined in a classpath library [359385] (target milestone: 3.5)
  • Deferred

    • Add an option to (not) generate the manifest when adding a Facet [349575] (target milestone: Future)
    • Add an option to (not) add the WTP classpath libraries when adding a Facet [349580] (target milestone: Future)

Web Profile

Starting in Java EE 6, the Web profile was introduced representing a subset of the full Java EE profile including EJB 3.1 lite, JPA 2.0, Servlet 3.0, and a few others. Providing a visual representation for this profile in current and future tools is needed to differentiate the capabilities of different containers.

Usability

WTP should continue to improve the experience for its users, and many of the Java EE wizards, properties, and scenarios can be improved

Other

Following are plan items that are not yet categorized into a theme.

  • Proposed

    • [API] Add the ability to specify the deployed archiveName for Jars/projects defined in a classpath library [359385] (target milestone: 3.5)
  • Deferred

    • Add an option to (not) generate the manifest when adding a Facet [349575] (target milestone: Future)
    • Add an option to (not) add the WTP classpath libraries when adding a Facet [349580] (target milestone: Future)

Table of Contents

Appendix References

  1. The general WTP plan can be found here.

Table of Contents

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