development/requirements/wtp_1_0_plan.html - www.eclipse.org/webtools - Git at Google

 <html>

 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
 <title>Eclipse Web Tools Project DRAFT 1.0 Plan</title>
 </head>

 <body>

 <h1>Eclipse Web Tools Project DRAFT 1.0 Plan</h1>

 <p><b>Initial draft</b> Mai 25, 2005 (by Jochen Krause / WTP Requirements Group
 based on WTP Project 0.7 Plan and Eclipse Project DRAFT 3.2 Plan)</p>
 <p><i>
 Please send comments about this <b>draft plan</b> to the </i>wtp-requirements@eclipse.org
 <i>mailing list.</i></p>

 <p>This document lays out the feature and API set for the next feature release
 of Eclipse Web Tools after 0.7, designated release 1.0. This document is a draft
 and is subject to change, we welcome all feedback. </p>
 <p>Web Tools 1.0 will be compatible with Eclipse 3.1 Releases.</p>
 <p>Plans do not materialize out of nowhere, nor are they entirely static. To
 ensure the planning process is transparent and open to the entire Eclipse
 community, we (the Eclipse Web Tools Requirement Group &amp; the Web Tools PMC) post
 plans in an embryonic form and revise them throughout the release cycle. </p>
 <p>The first part of the plan deals with the important matters of release
 deliverables, release milestones, target operating environments, and
 release-to-release compatibility. These are all things that need to be clear for
 any release, even if no features were to change.&nbsp; </p>
 <p>The remainder of the plan consists of plan items for the two subprojects
 under the Eclipse Web Tools top-level project. Each plan item covers a feature
 or API that is to be added to Web Tools, or some aspect of Web Tools that is to
 be improved. Each plan item will have its own entry in the Eclipse bugzilla
 database, with a title and a concise summary (usually a single paragraph) that
 explains the work item at a suitably high enough level so that everyone can
 readily understand what the work item is without having to understand the
 nitty-gritty detail. </p>
 <p>Not all plan items represent the same amount of work; some may be quite
 large, others, quite small. Some plan items may involve work that is localized
 to a single Platform component; others may involve coordinated changes to
 several components; other may pervade the entire Platform. Although some plan
 items are for work that is more pressing that others, the plan items appear in
 no particular order. </p>
 <p>With the previous release as the starting point, this is the plan for how we
 will enhance and improve it. Fixing bugs, improving test coverage,
 documentation, examples, performance tuning, usability, etc. are considered
 routine ongoing maintenance activities and are not included in this plan unless
 they would also involve a significant change to the API or feature set, or
 involve a significant amount of work. The intent of the plan is to account for
 all interesting feature work. </p>
 <p>&nbsp;</p>
 <p>The current status of each plan item is noted: </p>

     <p><b>High Priority</b> plan item - A
     high priority plan item is one that we have decided to address for the
     release (committed).</p>
     <p><b>Medium Priority</b> plan item -
     A medium priority plan item is one that we are considering addressing for
     the release. Although we are actively investigating it, we are not yet in a
     position to commit to it, or to say that we won't be able to address it. </p>
     <p><b>Low Priority </b>plan item  A
     low priority plan item is one that we addressed for a release we will only
     address that item if one component has addressed all high and medium
     priority items </p>
     <p><b>Deferred</b> plan item - A
     reasonable proposal that will not make it in to this release for some reason
     is marked as deferred with a brief note as to why it was deferred. Deferred
     plan items may resurface as committed plan items at a later point.</p>

 <h2>Release deliverables</h2>
 <p>The release deliverables have the same form as previous releases, namely: </p>
 <ul>
     <li>Source code release for Eclipse WTP
     Project, available as versions tagged &quot;R1_0&quot; in the Eclipse WTP Project
     </li>
     <li>CVS repository</li>
     <li>Eclipse WTP runtime binary and SDK
     download with all Eclipse pre-reqs (downloadable).</li>
     <li>Eclipse WTP runtime binary and SDK
     download (downloadable).</li>
 </ul>

 <h2>Release milestones</h2>

 <p>Release milestone occurring at roughly 6 week intervals and will be
 compatible with Eclipse 3.1 releases. Compatibility with Eclipse 3.2 milestone
 builds is not covered during the 1.0 release cycle. Eclipse 3.2 compatibility
 will be achieved with the Web Tools release following the 1.0 release, targeted
 for summer 2006. </p>
 <p>The milestones are:</p>
 <ul>
     <li>Friday September 23, 2005 - Milestone 8
     (1.0 M8) - stable build</li>
     <li>Friday Nov. 18, 2005 - Milestone 9
     (1.0 M9) - stable build</li>
     <li>Friday Dec. 16, 2005  Release 1.0
     - release build</li>
 </ul>

 <h2>Target Operating Environments</h2>

 <p>Eclipse WTP is built on the Eclipse platform itself. </p>
 <p>Most of the Eclipse WTP is &quot;pure&quot; Java code and has no direct dependence on
 the underlying operating system. The chief dependence is therefore on Eclipse.
 The 1.0 release of the Eclipse WTP Project is written and compiled against
 version 1.4 of the Java 2 Platform APIs, and targeted to run on version 1.4 and
 5.0 (1.5) of the Java 2 Runtime Environment, Standard Edition.</p>
 <p>Eclipse WTP is tested and validated on the following reference platforms
 (this list is updated over the course of the release cycle):</p>

 <table BORDER CELLSPACING="1" CELLPADDING="2" WIDTH="821">
   <tr>
     <td VALIGN="MIDDLE" COLSPAN="4" BGCOLOR="#cccccc">

     <p ALIGN="CENTER"><b>Eclipse WTP Reference Platforms</b><font FACE="Times New Roman" COLOR="#000080">
     </font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080"><b>Operating system</b></font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080"><b>Processor architecture</b></font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080"><b>Window system</b></font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080"><b>Java 2 Platform</b></font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
     Edition, version 1.4.2_06 for Microsoft Windows</font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Windows,
     Java 2 Technology Edition, Version 1.4.1</font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
     Edition, 1.4.2_05 for Linux x86</font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
     Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
     Edition, 1.4.2_06 for Linux x86</font></td>
   </tr>
   <tr>
     <td WIDTH="24%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
     <td WIDTH="14%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
     <td WIDTH="10%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
     <td WIDTH="52%" VALIGN="MIDDLE">
     <font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
     Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
   </tr>
 </table>

 <p>Although untested, Eclipse WTP should work fine on other OSes that support
 the same window system. See also
 <a HREF="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html/lTargetOperatingEnvironments">
 <u>Eclipse Target Operating
 Environments</u></a>
 </p>
 <p>Eclipse WTP is planned to support models for projects, editors, web and J2EE
 artefacts, servers. Whereas Eclipse WTP would not add OS dependencies to support
 the first three, projects, editors and artefacts, integrating servers to Eclipse
 WTP would imply some OS dependencies. Eclipse WTP is targeted to be OS
 independent through a modular conception. So, components for servers integration
 will be available out of Eclipse WTP Web, or J2EE, Standard Tools runtime binary
 distributions.</p>
 <p>Servers integrated into Eclipse WTP deliverables will be tested and validated
 on the same platforms listed above. Tests for other platforms will be relying on
 the community support.</p>

 <h3>Internationalization</h3>

 <p>The Eclipse WTP is designed as the basis for internationalized products. The
 user interface elements provided by the Eclipse SDK components, including
 dialogs and error messages, are externalized. The English strings are provided
 as the default resource bundles. Other language support, if any, will rely on
 the community support.</p>
 <h2>Compatibility with Other WTP Releases</h2>
 <p>Project Compatibility:</p>
 <ul>  <li>support for 0.7 projects </li>
 </ul>
 <p>Eclipse WTP deliverables will be compatible with Eclipse 3.1. No special
 attention will give for being compatible with previous Eclipse versions.</p>

 <h2>Eclipse WTP Subprojects</h2>

 <p>The Eclipse WTP consists of 2 subprojects. Each subproject is covered in its
 own section: </p>

 <a HREF="http://eclipse.org/webtools/wst/index.html">
     Web Standard Tools</a>

  <a HREF="http://eclipse.org/webtools/jst/index.html">
     J2EE Standard Tools</a>
 <p>For each subproject, the items listed reflect new features of the Web Tools
 Platform, or areas where existing features will be significantly reworked.
 Common goals are listed in the Common goals area.</p>
 <p>TBD [Each item indicates the components likely affected by that work item
 (many items involve coordinated changes to several components). Numbers in
 parentheses link to bugzilla problem reports for that plan item]</p>

 <h2>Common goals:</h2>
 <h3>Built to last</h3>
 <ul>
 <li>Platform

 <ul><li>Evolve available APIs and promote
       provisional APIs to platform APIs as appropriate (provisional APIs may
       disappear without replacement or be moved to other layers of the eclipse platform)
       </li>
       <li>Resolve API
       violations </li>
       <li><span >Extensibility (provide API to extend WTP
       with other specifications, e.g. JSF) </span></li>
 </ul></li>

 <li>Performance
 <ul>  <li>Memory Footprint </li>
       <li>Startup time</li>
       <li>Zero performance regression compared to 0.7</li>
       <li>Eliminating all critical performance
       problems (please report bugs)</li>
 </ul></li>

 <li>UI Consitency / Scalability
 <ul><li>Enforcement of
       Eclipse Guidelines </li>
       <li>Ease of use </li>
       <li>Common undo / redo in visual and text
       editors </li>
       </ul></li>
      <li>Online Help
      <ul><li>Providing more content</li>
      <li><span >Use dynamic system</span></li>
      <li>Fix National Language bugs.</li>
      <li>Fix Accessibility bugs</li>
      </ul></li>

  <li>Improve feature split
      <ul>
       <li>Componentize WTP into Features to enable adopters to select subsets of function</li>
      <li>Community feedback welcome</li>
      </ul></li>
 </ul>


 <h2><span >Web Standard Tools
 subproject</span></h2>


 <h3><span >Built to last</span></h3>


 <p><span >Evolve
 available APIs and promote provisional APIs to platform APIs for the following
 components (provisional APIs may disappear without replacement or be moved to
 other layers of the eclipse platform)</span></p>


 <ul type="disc">
 <li><span >Command </span></li><li><span >Navigator</span></li><li><span >Snippets</span></li><li><span >SSE (CSS, DTD, HTML, XML)</span></li><li><span >Web Services</span></li>
 </ul>


 <h2><span >J2EE Standard Tools</span></h2>


 <h3><span >Built to last</span></h3>


 <p><span>Evolve
 available APIs and promote provisional APIs to platform APIs for the following
 components (provisional APIs may disappear without replacement or be moved to
 other layers of the eclipse platform)</span></p>


 <ul type="disc">
 <li><span >JSP</span></li>
 <li><span >Flexible Project Structure </span></li>
 <li><span >Component Features</span></li>
 <li><span >Server</span></li>
 </ul>


 <h3>Server Runtime</h3>


 <ul type="disc">
 <li><span >Support for JBoss, WebSphere, WebLogic</span></li>
 </ul>


 </body>

 </html>
	<html>

	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
	<title>Eclipse Web Tools Project DRAFT 1.0 Plan</title>
	</head>

	<body>

	<h1>Eclipse Web Tools Project DRAFT 1.0 Plan</h1>

	<p><b>Initial draft</b> Mai 25, 2005 (by Jochen Krause / WTP Requirements Group
	based on WTP Project 0.7 Plan and Eclipse Project DRAFT 3.2 Plan)</p>
	<p><i>
	Please send comments about this <b>draft plan</b> to the </i>wtp-requirements@eclipse.org
	<i>mailing list.</i></p>

	<p>This document lays out the feature and API set for the next feature release
	of Eclipse Web Tools after 0.7, designated release 1.0. This document is a draft
	and is subject to change, we welcome all feedback. </p>
	<p>Web Tools 1.0 will be compatible with Eclipse 3.1 Releases.</p>
	<p>Plans do not materialize out of nowhere, nor are they entirely static. To
	ensure the planning process is transparent and open to the entire Eclipse
	community, we (the Eclipse Web Tools Requirement Group & the Web Tools PMC) post
	plans in an embryonic form and revise them throughout the release cycle. </p>
	<p>The first part of the plan deals with the important matters of release
	deliverables, release milestones, target operating environments, and
	release-to-release compatibility. These are all things that need to be clear for
	any release, even if no features were to change.  </p>
	<p>The remainder of the plan consists of plan items for the two subprojects
	under the Eclipse Web Tools top-level project. Each plan item covers a feature
	or API that is to be added to Web Tools, or some aspect of Web Tools that is to
	be improved. Each plan item will have its own entry in the Eclipse bugzilla
	database, with a title and a concise summary (usually a single paragraph) that
	explains the work item at a suitably high enough level so that everyone can
	readily understand what the work item is without having to understand the
	nitty-gritty detail. </p>
	<p>Not all plan items represent the same amount of work; some may be quite
	large, others, quite small. Some plan items may involve work that is localized
	to a single Platform component; others may involve coordinated changes to
	several components; other may pervade the entire Platform. Although some plan
	items are for work that is more pressing that others, the plan items appear in
	no particular order. </p>
	<p>With the previous release as the starting point, this is the plan for how we
	will enhance and improve it. Fixing bugs, improving test coverage,
	documentation, examples, performance tuning, usability, etc. are considered
	routine ongoing maintenance activities and are not included in this plan unless
	they would also involve a significant change to the API or feature set, or
	involve a significant amount of work. The intent of the plan is to account for
	all interesting feature work. </p>
	<p> </p>
	<p>The current status of each plan item is noted: </p>

	<p><b>High Priority</b> plan item - A
	high priority plan item is one that we have decided to address for the
	release (committed).</p>
	<p><b>Medium Priority</b> plan item -
	A medium priority plan item is one that we are considering addressing for
	the release. Although we are actively investigating it, we are not yet in a
	position to commit to it, or to say that we won't be able to address it. </p>
	<p><b>Low Priority </b>plan item A
	low priority plan item is one that we addressed for a release we will only
	address that item if one component has addressed all high and medium
	priority items </p>
	<p><b>Deferred</b> plan item - A
	reasonable proposal that will not make it in to this release for some reason
	is marked as deferred with a brief note as to why it was deferred. Deferred
	plan items may resurface as committed plan items at a later point.</p>

	<h2>Release deliverables</h2>
	<p>The release deliverables have the same form as previous releases, namely: </p>
	<ul>
	<li>Source code release for Eclipse WTP
	Project, available as versions tagged "R1_0" in the Eclipse WTP Project
	</li>
	<li>CVS repository</li>
	<li>Eclipse WTP runtime binary and SDK
	download with all Eclipse pre-reqs (downloadable).</li>
	<li>Eclipse WTP runtime binary and SDK
	download (downloadable).</li>
	</ul>

	<h2>Release milestones</h2>

	<p>Release milestone occurring at roughly 6 week intervals and will be
	compatible with Eclipse 3.1 releases. Compatibility with Eclipse 3.2 milestone
	builds is not covered during the 1.0 release cycle. Eclipse 3.2 compatibility
	will be achieved with the Web Tools release following the 1.0 release, targeted
	for summer 2006. </p>
	<p>The milestones are:</p>
	<ul>
	<li>Friday September 23, 2005 - Milestone 8
	(1.0 M8) - stable build</li>
	<li>Friday Nov. 18, 2005 - Milestone 9
	(1.0 M9) - stable build</li>
	<li>Friday Dec. 16, 2005 Release 1.0
	- release build</li>
	</ul>

	<h2>Target Operating Environments</h2>

	<p>Eclipse WTP is built on the Eclipse platform itself. </p>
	<p>Most of the Eclipse WTP is "pure" Java code and has no direct dependence on
	the underlying operating system. The chief dependence is therefore on Eclipse.
	The 1.0 release of the Eclipse WTP Project is written and compiled against
	version 1.4 of the Java 2 Platform APIs, and targeted to run on version 1.4 and
	5.0 (1.5) of the Java 2 Runtime Environment, Standard Edition.</p>
	<p>Eclipse WTP is tested and validated on the following reference platforms
	(this list is updated over the course of the release cycle):</p>

	<table BORDER CELLSPACING="1" CELLPADDING="2" WIDTH="821">
	<tr>
	<td VALIGN="MIDDLE" COLSPAN="4" BGCOLOR="#cccccc">

	<p ALIGN="CENTER"><b>Eclipse WTP Reference Platforms</b><font FACE="Times New Roman" COLOR="#000080">
	</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080"><b>Operating system</b></font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080"><b>Processor architecture</b></font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080"><b>Window system</b></font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080"><b>Java 2 Platform</b></font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
	Edition, version 1.4.2_06 for Microsoft Windows</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Microsoft Windows XP</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Win32</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Windows,
	Java 2 Technology Edition, Version 1.4.1</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
	Edition, 1.4.2_05 for Linux x86</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Red Hat Enterprise Linux WS 3</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
	Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Sun Java 2 SDK, Standard
	Edition, 1.4.2_06 for Linux x86</font></td>
	</tr>
	<tr>
	<td WIDTH="24%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">SuSE Linux 8.3</font></td>
	<td WIDTH="14%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">Intel x86</font></td>
	<td WIDTH="10%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">GTK</font></td>
	<td WIDTH="52%" VALIGN="MIDDLE">
	<font FACE="Times New Roman" COLOR="#000080">IBM 32-bit SDK for Linux on
	Intel architecture, Java 2 Technology Edition, Version 1.4.2</font></td>
	</tr>
	</table>

	<p>Although untested, Eclipse WTP should work fine on other OSes that support
	the same window system. See also
	<a HREF="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html/lTargetOperatingEnvironments">
	<u>Eclipse Target Operating
	Environments</u></a>
	</p>
	<p>Eclipse WTP is planned to support models for projects, editors, web and J2EE
	artefacts, servers. Whereas Eclipse WTP would not add OS dependencies to support
	the first three, projects, editors and artefacts, integrating servers to Eclipse
	WTP would imply some OS dependencies. Eclipse WTP is targeted to be OS
	independent through a modular conception. So, components for servers integration
	will be available out of Eclipse WTP Web, or J2EE, Standard Tools runtime binary
	distributions.</p>
	<p>Servers integrated into Eclipse WTP deliverables will be tested and validated
	on the same platforms listed above. Tests for other platforms will be relying on
	the community support.</p>

	<h3>Internationalization</h3>

	<p>The Eclipse WTP is designed as the basis for internationalized products. The
	user interface elements provided by the Eclipse SDK components, including
	dialogs and error messages, are externalized. The English strings are provided
	as the default resource bundles. Other language support, if any, will rely on
	the community support.</p>
	<h2>Compatibility with Other WTP Releases</h2>
	<p>Project Compatibility:</p>
	<ul> <li>support for 0.7 projects </li>
	</ul>
	<p>Eclipse WTP deliverables will be compatible with Eclipse 3.1. No special
	attention will give for being compatible with previous Eclipse versions.</p>

	<h2>Eclipse WTP Subprojects</h2>

	<p>The Eclipse WTP consists of 2 subprojects. Each subproject is covered in its
	own section: </p>

	<a HREF="http://eclipse.org/webtools/wst/index.html">
	Web Standard Tools</a>

	<a HREF="http://eclipse.org/webtools/jst/index.html">
	J2EE Standard Tools</a>
	<p>For each subproject, the items listed reflect new features of the Web Tools
	Platform, or areas where existing features will be significantly reworked.
	Common goals are listed in the Common goals area.</p>
	<p>TBD [Each item indicates the components likely affected by that work item
	(many items involve coordinated changes to several components). Numbers in
	parentheses link to bugzilla problem reports for that plan item]</p>

	<h2>Common goals:</h2>
	<h3>Built to last</h3>
	<ul>
	<li>Platform

	<ul><li>Evolve available APIs and promote
	provisional APIs to platform APIs as appropriate (provisional APIs may
	disappear without replacement or be moved to other layers of the eclipse platform)
	</li>
	<li>Resolve API
	violations </li>
	<li><span >Extensibility (provide API to extend WTP
	with other specifications, e.g. JSF) </span></li>
	</ul></li>

	<li>Performance
	<ul> <li>Memory Footprint </li>
	<li>Startup time</li>
	<li>Zero performance regression compared to 0.7</li>
	<li>Eliminating all critical performance
	problems (please report bugs)</li>
	</ul></li>

	<li>UI Consitency / Scalability
	<ul><li>Enforcement of
	Eclipse Guidelines </li>
	<li>Ease of use </li>
	<li>Common undo / redo in visual and text
	editors </li>
	</ul></li>
	<li>Online Help
	<ul><li>Providing more content</li>
	<li><span >Use dynamic system</span></li>
	<li>Fix National Language bugs.</li>
	<li>Fix Accessibility bugs</li>
	</ul></li>

	<li>Improve feature split
	<ul>
	<li>Componentize WTP into Features to enable adopters to select subsets of function</li>
	<li>Community feedback welcome</li>
	</ul></li>
	</ul>


	<h2><span >Web Standard Tools
	subproject</span></h2>


	<h3><span >Built to last</span></h3>


	<p><span >Evolve
	available APIs and promote provisional APIs to platform APIs for the following
	components (provisional APIs may disappear without replacement or be moved to
	other layers of the eclipse platform)</span></p>


	<ul type="disc">
	<li><span >Command </span></li><li><span >Navigator</span></li><li><span >Snippets</span></li><li><span >SSE (CSS, DTD, HTML, XML)</span></li><li><span >Web Services</span></li>
	</ul>


	<h2><span >J2EE Standard Tools</span></h2>


	<h3><span >Built to last</span></h3>


	<p><span>Evolve
	available APIs and promote provisional APIs to platform APIs for the following
	components (provisional APIs may disappear without replacement or be moved to
	other layers of the eclipse platform)</span></p>


	<ul type="disc">
	<li><span >JSP</span></li>
	<li><span >Flexible Project Structure </span></li>
	<li><span >Component Features</span></li>
	<li><span >Server</span></li>
	</ul>


	<h3>Server Runtime</h3>


	<ul type="disc">
	<li><span >Support for JBoss, WebSphere, WebLogic</span></li>
	</ul>


	</body>

	</html>