Project Plan For WTP Common Tools, version 3.1

Introduction

The Web Tool Platform (WTP) project provides extensible frameworks and exemplary tools to build Web and Java EE applications. The WTP Common Tools subproject includes the following features

1. Faceted Project Framework
2. Validation Framework

This document describes the features and the API set in the WTP Common 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

Table of Contents

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

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

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 WTP Common 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
  • No items.

• Proposed
  • No items.

• Deferred
  • No items.

Other

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

• Committed
  • Facets should provide a preference scope for storing related information [207526] (target milestone: 3.1 M3)
  • Need more extensible library provider framework [246448] (target milestone: 3.1 M3)
  • User library provider should support custom validation [251947] (target milestone: 3.1 M4)
  • User library provider should remember it's last state [251949] (target milestone: 3.1 M3)
  • LibraryInstallDelegate.refresh() should be desclared as public [253026] (target milestone: 3.1 RC3)
  • User should be able to disable library configuration for a facet [254790] (target milestone: 3.1 M4)
  • [UI] Java facet needs install page for source and output dir config [116469] (target milestone: 3.1 M1)
  • Faceted Project creation wizard should support working sets [243488] (target milestone: 3.1 M1)

• Proposed
  • Data models of contributed wizard pages are not loaded if the wizard is finished on the first page [216924] (target milestone: 3.1)
  • Support easy downloading of libraries [253033] (target milestone: 3.1)
  • Allow for customized search scopes [249528] (target milestone: 3.1)
  • Mark a facet unsupported for a runtime [120376] (target milestone: 3.1)
  • Support dynamic help for individual facets. [135950] (target milestone: 3.1)
  • Allow dynamic page sets to be associated with facet actions [154718] (target milestone: 3.1)
  • Facet bridge called 1034 times when opening dialog [169846] (target milestone: 3.1)
  • Need PROJECT_INITIALIZED event [198165] (target milestone: 3.1)
  • Allow filtering by facets on org.eclipse.wst.common.project.facet.core.listeners ext-pt [200962] (target milestone: 3.1)
  • Need an action to make an existing project faceted [210541] (target milestone: 3.1)
  • allowing testing for project facets that are not defined [223650] (target milestone: 3.1)
  • defaultFacets extension point should support optional contributions [251722] (target milestone: 3.1)
  • Add the ability to deprecate a facet [255038] (target milestone: 3.1)
  • Facet repair action needed [163401] (target milestone: 3.1)
  • Allow facet constraints to conditionally ignore facets not present in an install [197557] (target milestone: 3.1)

• Deferred
  • No items.

Table of Contents

Appendix References

1. The general WTP plan can be found here.

Table of Contents