Project Plan For WTP Java EE Tools, 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 in the Java EE Tools subproject for the Galileo release.
Release Deliverables
- WTP non-SDK package
- WTP SDK Package
- WST non-SDK package
- WST SDK Package
- The Eclipse IDE for JEE Developers package
Release Milestones
WTP Milestones follow the Eclipse release milestones by an offset of 2 as set by the Galileo release schedule.
| M1 | 8/31/2008 | M1 milestone |
| M2 | 10/01/2008 | M2 milestone. |
| M3 | 11/12/2008 | M3 milestone |
| M4 | 12/29/2008 | M4 milestone |
| M5 | 2/06/2009 | M5 milestone |
| M6 | 3/12/2009 | M6 milestone.Feature complete, API and UI Freeze |
| M7 | 5/05/2009 | M7 milestone. PMC review starts |
| RC1 | 5/19/2009 | RC1 milestone.PMC approval required, 1 vote required |
| RC2 | 5/26/2009 | RC2 milestone.PMC approval required, 2 votes required |
| RC3 | 6/02/2009 | RC3 milestone.Document Freeze. PMC approval required, 3 votes required |
| RC4 | 6/09/2009 | RC4 milestone.Only stop-ship defects, PMC approval required, 3 vote required |
| RC5 | 6/16/2009 | RC5 milestone.Only stop-ship defects, PMC approval required, 3 vote required |
| GA | 6/26/2009 | GA |
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.
Compatibility with Previous Releases
Themes and Priorities
Themes and their priorities communicate the main objectives of the project and their importance. The following themes are derived from those defined by the Eclipse Requirement council for the Eclipse Galileo release and from the WTP 3.0 release themes. These will be prioritized based on the community feedback. New themes could be synthesized from the requirements submitted by the community.
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.
Ease of Use
Features provided by WTP should be simple to use for users with widely-varying backgrounds and skill sets.
- WTP User Interface should be consistent and should follow the Eclipse User Experience Guidelines.
- Usability and Accessibility reviews should be done for the most common task flows. Cheat Sheets should be provided to assist users in performing tasks
- WTP should provide enhanced user documentation, tutorials, white papers, demonstrations.
- Committed
- Proposed
- Register jsp to web.xml is not user friendly [219304] (target milestone: 3.1)
- remove library action from Deployment Descriptor node for ear5 projects [239196] (target milestone: 3.1)
- Input field in EAR wizard last page has a different look than other fields. [212327] (target milestone: 3.1)
- New Servlet wizard page lacks shortcuts [198937] (target milestone: 3.1)
- Delete servlet refactoring [138173] (target milestone: 3.1)
- Creating a Servlet from an existing Servlet class or JSP file [238770] (target milestone: 3.1)
- Creating a Filter from a Servlet class or JSP file [238771] (target milestone: 3.1)
- [project creation] Should alert the user if they enter a non-existing ear projec name [132203] (target milestone: 3.1)
- Generate Deployment Descriptor Stub on Deployment Descriptor Node [226933] (target milestone: 3.1)
- Deferred
Java EE 6
WTP should be up-to-date with supporting the latest Java EE specification level. JSR-316 defines the latest Java EE 6 specification.
- Committed
- No items.
- Proposed
- Deferred
- Servlet 3.0 tooling support [252616] (target milestone: Future)
Other
Following are plan items that are not yet categorized into a theme.
- Committed
- Preference for statically compiled JET templates [250128] (target milestone: 3.1 M4)
- Proposed
- Support for upgrading EE spec level [194926] (target milestone: 3.1)
- Adding Java EE 5 modules to legacy(1.4) EAR [229893] (target milestone: 3.1)
- Allowing Java EE Utility projects to be changed to Web/EJB projects [242736] (target milestone: 3.1)
- Move all constants used in JEE plugins in public interfaces [239598] (target milestone: 3.1)
- Write mode for Java EE models [242722] (target milestone: 3.1)
- Deferred
Appendix References
- The general WTP plan can be found here.
