Remove oudated information from repo (#3)
* Remove oudated information from repo
First round of cleanups, for #2
* Remove oudated information from repo
Second round of cleanups, for #2
diff --git a/development/2_0_retrospective_actions.html b/development/2_0_retrospective_actions.html
deleted file mode 100644
index 306c5e9..0000000
--- a/development/2_0_retrospective_actions.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-
-<html>
-<head>
-
- <link rel="stylesheet" href="../../default_style.css" type="text/css">
- <title>Eclipse 2.0 Retrospective Actions</title>
- <meta name="Author" content="Eclipse Project PMC">
-
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
- <body>
-
-<h1>Eclipse 2.0 Retrospective Actions</h1>
-<p>August 29, 2002</p>
-<p>In August 2002 retrospective sessions were held with the various component
- teams to discuss what worked (and didn't work) with the 2.0 release. Based on
- the feedback collected during these sessions, we agreed on the following actions
- for the 2.1 effort.</p>
-<h2>Actions</h2>
-<ol>
- <li> <b>We will actively and visibly track issues.</b>
- <ul>
- <li>We will publish a top ten issues list and track it on the Eclipse web.</li>
- <li>Many issues span components; these issues will be addressed by <i>dynamic
- teams</i> with members from different components. Dynamic teams will have
- team leads that are responsible for delivering the resolution to an issue.</li>
- </ul>
- </li>
- <li><b> We will continue to work in monthly time boxes.</b>
- <ul>
- <li>There will be a milestone defined for each time box.</li>
- <li>Teams make their milestone plans accessible on the Eclipse web. </li>
- <li> We will do a an <i>"everybody tests" day</i> at the end of
- each milestone.</li>
- <li>We will reserve time for writing tests in each time box.</li>
- <li>Each team will develop on their latest code (<i>daily plug-in export</i>).</li>
- </ul>
- </li>
- <li><b>We will improve bug handling</b>.
- <ul>
- <li>First line bug triage will be off-loaded from the component owners.</li>
- <li>We will document and follow the same bug work flow in all components.</li>
- <li>We will make the current bug situation visible on the Web in the form
- of a chart that is updated automatically.</li>
- <li>We will investigate Bugzilla UI improvements.</li>
- </ul>
- </li>
- <li><b>We will make the planning process more visible</b>.
- <ul>
- <li>We will make a <i>proto 2.1</i> plan available early in the release
- cycle.</li>
- <li>We will have weekly planning update meetings.
- <ul>
- <li>Each component lead will give a concise status about what has happened
- last week and what is planned for next week.</li>
- <li>The meeting minutes will be made available on eclipse-dev developer
- mailing list.</li>
- </ul>
- </li>
- </ul>
- </li>
- <li><b>We will provide an additional channel for quick interactions.</b>
- <ul>
- <li>Committers will be connected to instant messaging (need to decide about
- the tool).</li>
- </ul>
- </li>
- <li><b>We will improve the Eclipse Web portal</b>
- <ul>
- <li>We will improve navigability.</li>
- <li>We will separate the user from the developer domain.</li>
- <li>We will provide support for contributing announcements.</li>
- <li>We will refactor the newsgroups (to separate users from developers).</li>
- </ul>
- </li>
- <li><b>We will improve the way we do documentation.</b>
- <ul>
- <li>We will define a style guide and agree on tools.</li>
- <li>We plan and test documentation as part of the development process.</li>
- <li>We will invest in tools that make the checking less painful.</li>
- <li>We will provide content earlier.</li>
- </ul>
- </li>
-</ol>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/eclipse-charter-old.html b/eclipse-charter-old.html
deleted file mode 100644
index ce8e386..0000000
--- a/eclipse-charter-old.html
+++ /dev/null
@@ -1,739 +0,0 @@
-<html xmlns:v="urn:schemas-microsoft-com:vml"
-xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 9">
-<meta name=Originator content="Microsoft Word 9">
-<link rel=File-List href="./eclipse-charter_files/filelist.xml">
-<link rel=Edit-Time-Data href="./eclipse-charter_files/editdata.mso">
-<!--[if !mso]>
-<style>
-v\:* {behavior:url(#default#VML);}
-o\:* {behavior:url(#default#VML);}
-w\:* {behavior:url(#default#VML);}
-.shape {behavior:url(#default#VML);}
-</style>
-<![endif]-->
-<title>Eclipse Tools Project</title>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
- <o:Author>Dave Thomson</o:Author>
- <o:LastAuthor>Dave Thomson</o:LastAuthor>
- <o:Revision>2</o:Revision>
- <o:TotalTime>8</o:TotalTime>
- <o:Created>2001-11-25T03:37:00Z</o:Created>
- <o:LastSaved>2001-11-25T03:37:00Z</o:LastSaved>
- <o:Pages>2</o:Pages>
- <o:Words>2527</o:Words>
- <o:Characters>14406</o:Characters>
- <o:Lines>120</o:Lines>
- <o:Paragraphs>28</o:Paragraphs>
- <o:CharactersWithSpaces>17691</o:CharactersWithSpaces>
- <o:Version>9.2720</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
- <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
- </w:WordDocument>
-</xml><![endif]-->
-<style>
-<!--
- /* Font Definitions */
-@font-face
- {font-family:Wingdings;
- panose-1:5 0 0 0 0 0 0 0 0 0;
- mso-font-charset:2;
- mso-generic-font-family:auto;
- mso-font-pitch:variable;
- mso-font-signature:0 268435456 0 0 -2147483648 0;}
-@font-face
- {font-family:Verdana;
- panose-1:2 11 6 4 3 5 4 4 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:647 0 0 0 159 0;}
- /* Style Definitions */
-p.MsoNormal, li.MsoNormal, div.MsoNormal
- {mso-style-parent:"";
- margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- font-size:12.0pt;
- font-family:"Times New Roman";
- mso-fareast-font-family:"Times New Roman";}
-h1
- {margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- mso-outline-level:1;
- font-size:21.0pt;
- font-family:Arial;
- mso-font-kerning:18.0pt;
- font-weight:bold;}
-h2
- {margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-line-height-alt:10.5pt;
- mso-pagination:widow-orphan;
- mso-outline-level:2;
- font-size:18.0pt;
- font-family:Arial;
- font-weight:bold;}
-h3
- {margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- mso-outline-level:3;
- font-size:14.0pt;
- font-family:Arial;
- font-weight:bold;}
-a:link, span.MsoHyperlink
- {color:blue;
- text-decoration:underline;
- text-underline:single;}
-a:visited, span.MsoHyperlinkFollowed
- {color:blue;
- text-decoration:underline;
- text-underline:single;}
-p
- {margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- font-size:10.0pt;
- font-family:Arial;
- mso-fareast-font-family:"Times New Roman";}
-code
- {mso-ascii-font-family:"Courier New";
- mso-fareast-font-family:"Courier New";
- mso-hansi-font-family:"Courier New";
- mso-bidi-font-family:"Courier New";}
-pre
- {margin:0in;
- margin-bottom:.0001pt;
- mso-pagination:widow-orphan;
- tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
- font-size:10.0pt;
- font-family:"Courier New";
- mso-fareast-font-family:"Courier New";}
-p.indextop, li.indextop, div.indextop
- {mso-style-name:indextop;
- margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- font-size:24.0pt;
- font-family:Verdana;
- mso-fareast-font-family:"Times New Roman";
- mso-bidi-font-family:Arial;
- font-weight:bold;}
-p.indexsub, li.indexsub, div.indexsub
- {mso-style-name:indexsub;
- margin-right:0in;
- mso-margin-top-alt:auto;
- mso-margin-bottom-alt:auto;
- margin-left:0in;
- mso-pagination:widow-orphan;
- font-size:7.5pt;
- font-family:Arial;
- mso-fareast-font-family:"Times New Roman";
- color:#8080FF;}
-@page Section1
- {size:8.5in 11.0in;
- margin:1.0in 1.25in 1.0in 1.25in;
- mso-header-margin:.5in;
- mso-footer-margin:.5in;
- mso-paper-source:0;}
-div.Section1
- {page:Section1;}
- /* List Definitions */
-@list l0
- {mso-list-id:97258917;
- mso-list-type:hybrid;
- mso-list-template-ids:938493464 -1722270466 1328035828 162058584 -1583577958 1708689942 358257648 -789267326 1364346306 1905806722;}
-@list l0:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;
- mso-ansi-font-size:10.0pt;
- font-family:Symbol;}
-@list l1
- {mso-list-id:1140729447;
- mso-list-type:hybrid;
- mso-list-template-ids:-548665272 99540706 454694258 918687008 -856886194 92689176 392868292 981366132 -2098539492 -955852746;}
-@list l1:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;
- mso-ansi-font-size:10.0pt;
- font-family:Symbol;}
-@list l2
- {mso-list-id:2083134086;
- mso-list-type:hybrid;
- mso-list-template-ids:-2080353412 1356621094 -131857262 -1447128774 -425566188 1893082798 1171154726 2031539886 1440021566 -1653822288;}
-@list l2:level1
- {mso-level-number-format:bullet;
- mso-level-text:\F0B7;
- mso-level-tab-stop:.5in;
- mso-level-number-position:left;
- text-indent:-.25in;
- mso-ansi-font-size:10.0pt;
- font-family:Symbol;}
-ol
- {margin-bottom:0in;}
-ul
- {margin-bottom:0in;}
--->
-</style>
-</head>
-
-<body lang=EN-CA link=blue vlink=blue style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<table border=0 cellspacing=5 cellpadding=0 width="100%" style='width:100.0%;
- mso-cellspacing:3.7pt;margin-left:8.5pt;mso-padding-alt:1.5pt 1.5pt 1.5pt 1.5pt'>
- <tr>
- <td colspan=2 valign=top style='background:#0080C0;padding:1.5pt 1.5pt 1.5pt 1.5pt'>
- <p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Arial;
- color:white'>Eclipse Project Charter - v0.52</span></b><span
- style='font-size:10.0pt;font-family:Arial'><o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'>
- <p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Arial'>Overview</span></b><span
- style='font-size:10.0pt;font-family:Arial'><br>
- The Eclipse Project is a collaborative software development project dedicated
- to providing a robust, full-featured, commercial-quality, and freely
- available industry platform for the development of highly integrated tools.
- This document describes the composition and organization of the project,
- roles and responsibilities of the participants, and development process for
- the project. The project charter is a living document that will be updated to
- reflect the evolution of the development process evolves over time.<o:p></o:p></span></p>
- <p><b>Mission</b><br>
- Eclipse is a kind of universal tool platform - an open extensible IDE for
- anything and yet nothing in particular. The real value comes from tool
- plug-ins that "teach" Eclipse how to work with things - java files,
- web content, graphics, video - almost anything one can imagine. Eclipse
- allows tool builders to independently develop tools that integrate with other
- people's tools so seamlessly you can't tell where one tool ends and another
- starts.</p>
- <p>The success of Eclipse depends on how well it enables a wide range of tool
- builders to build best of breed integrated tools. But the real vision of
- Eclipse as an industry platform is only realized if these tools from
- different tool builders can be combined together by users to suit their
- unique requirements, in ways that the tool builders never even imagined. </p>
- <p>The mission of the Eclipse Project is to adapt and evolve the Eclipse
- technology to meet the needs of the Eclipse tool building community and its
- users, so that the vision of Eclipse as an industry platform is realized.</p>
- <p><b>Scope</b><br>
- The Eclipse Project encompasses both the Eclipse platform technology itself,
- and a set of tools that together form the software development kit (SDK) for
- building Eclipse-based tools. The Eclipse Project will be structured into the
- following subprojects:</p>
- <ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l1 level1 lfo1;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Platform - the platform upon
- which all other Eclipse based tools are built. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l1 level1 lfo1;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>JDT - The Java development
- tooling, or Java IDE. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l1 level1 lfo1;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>PDE - Plug-in development
- environment. <o:p></o:p></span></li>
- </ul>
- <p><img width=435 height=134 id="_x0000_i1025"
- src="eclipse-structure.gif"></p>
- <p> </p>
- <p>The Platform subproject is further subdivided into the following
- components:</p>
- <table border=0 cellpadding=0 width="75%" style='width:75.0%;mso-cellspacing:
- 1.5pt'>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Ant<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Ant
- Java based build tool<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Compare<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Universal
- Compare Facility<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Core<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Core
- libraries<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Debug<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Universal
- Debugger<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Help<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Help
- system<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Scripting<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Scripting
- support<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Search<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Integrated
- Search Facility<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>SWT<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Standard
- Widget Toolkit<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>UI<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>User
- Interface libraries<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Update<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Dynamic
- Update/Install/Field Service<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>VCM<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Versioning
- and Configuration Management<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>WebDAV<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>WebDAV
- integration<o:p></o:p></span></p>
- </td>
- </tr>
- </table>
- <p>The JDT subproject is further subdivided into the following components:</p>
- <table border=0 cellpadding=0 width="75%" style='width:75.0%;mso-cellspacing:
- 1.5pt'>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>JDT
- Core<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Compiler
- and Builder<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>JDT UI<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Java
- IDE User Interface<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>JDt
- Debug<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>Debug
- support for Java<o:p></o:p></span></p>
- </td>
- </tr>
- </table>
- <p>The PDE subproject is further subdivided into the following components:</p>
- <table border=0 cellpadding=0 width="75%" style='width:75.0%;mso-cellspacing:
- 1.5pt'>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>PDE
- Core<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>PDE
- Build<o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td width="25%" style='width:25.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>PDE UI<o:p></o:p></span></p>
- </td>
- <td width="75%" style='width:75.0%;padding:.75pt .75pt .75pt .75pt'>
- <p class=MsoNormal><span style='font-size:10.0pt;font-family:Arial'>PDE
- User Interface<o:p></o:p></span></p>
- </td>
- </tr>
- </table>
- <p><b>Project Management Committee</b><a name=PMC></a><br>
- The Eclipse Project is managed by a small group known as the Eclipse Project
- Management Committee [Eclipse PMC].</p>
- <p>The Eclipse PMC is responsible for the strategic direction and success of
- the Eclipse Project. This governing and advisory body is expected to ensure
- the project's welfare and guide its overall direction. The PMC is responsible
- for overall development direction, conflict resolution, development processes
- and infrastructure, and the overall technical success of the project.</p>
- <p>The PMC has the following responsibilities:</p>
- <ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Providing the leadership and
- vision to guide the project's overall direction. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Providing assistance and
- support to the developers working on the project by removing obstacles,
- solving problems, and resolving conflicts. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Ensuring that subproject
- plans are produced, and presenting these plans to the Board. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Establishing the development
- processes and infrastructure needed for the development team to be
- effective. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Recommending new subprojects
- to the Board, if appropriate, and appointing the subproject lead. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Establishing the initial set
- of subproject committers, and establishing the procedures for voting in
- new committers. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Helping to ensure that subprojects
- have enough contributors, and helping to fill vacancies in roles. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Producing “how to get
- involved” guidelines to help new potential contributors get started.<o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Coordinating relationships
- with other eclipse.org projects. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Facilitating code or other donations
- by individuals or companies. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Ensures licensing is
- compatible with licensing established by board. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l0 level1 lfo2;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Representing the project to
- the outside world. <o:p></o:p></span></li>
- </ul>
- <p>The PMC Lead is appointed by the Board. The initial PMC is selected by the
- PMC Lead. Thereafter, to become a member of the PMC, an individual must be
- nominated by a member of the PMC, and unanimously approved by all PMC
- members. The goal is to keep the membership of the PMC very small.</p>
- <p>In the unlikely event that a member of the PMC becomes disruptive to the
- process or ceases to contribute for an extended period, the member may be
- removed by unanimous vote of remaining PMC members.</p>
- <p>The PMC is responsible for producing and maintaining the project charter.
- Development must conform to any rules or processes outlined in the charter,
- so a change to the development process may necessitate a change to the
- charter.</p>
- <p>The work of the PMC is shared by the PMC members. All PMC members are
- expected to contribute actively. In particular, PMC members are expected to
- take responsibility for overseeing certain areas of work in the project, and
- reporting to the PMC on these areas.</p>
- <p>Active participation in the user newsgroup and the appropriate developer
- mailing lists is a responsibility of all PMC members, and is critical to the
- success of the project. PMC members are required to monitor the main project
- mailing list, and the developer mailing lists for all subprojects and
- components they are overseeing.</p>
- <p><b>Roles</b><br>
- The Eclipse Project is a meritocracy -- the more you contribute, and the
- higher the quality of your contribution, the more you are allowed to do.
- However with this comes increased responsibility.</p>
- <p><b>Users</b><br>
- Users are the people who use the products that the Project produces. People
- in this role aren't contributing code, but they are using the products,
- reporting bugs, and making feature requests and suggestions. Users are
- encouraged to participate through the user newsgroup(s), asking questions,
- providing suggestions, and helping other users. Users are also encouraged to
- report problem reports using the bug tracking system. </p>
- <p><b>Developers</b><br>
- Users who contribute code or documentation become developers. Developers are
- the people who contribute code, fixes, documentation, or other work that goes
- into the product. Developers are also encouraged to participate in the user
- newsgroup(s), and should monitor the developer mailing list associated with
- their area of contribution. When appropriate, developers may also contribute
- to development design discussions related to their area of contribution.
- Developers are expected to be proactive in reporting problems in the bug
- tracking system.</p>
- <p><b>Committers</b><br>
- Developers who give frequent and valuable contributions to a subproject, or
- component of a subproject (in the case of large subprojects), can have their
- status promoted to that of a "Committer" for that subproject or
- component respectively. A Committer has write access to the source code
- repository for the associated subproject (or component), and gains voting
- rights allowing them to affect the future of the subproject (or component).</p>
- <p>In order for a Developer to become a Committer, another Committer for the
- subproject (or component) can nominate that Developer or the Developer can
- ask for it. Once a Developer is nominated, the Committers for the subproject
- (or component) will vote. If there are at least 3 positive votes and no
- negative votes, the Developer is recommended to the PMC for commit
- privileges. If the PMC approves, the Developer is converted into a Committer
- and given write access to the source code repository for that subproject (or
- component). Becoming a Committer is a privilege that is earned by
- contributing and showing discipline and good judgement. It is a
- responsibility that should be neither given nor taken lightly</p>
- <p>At times, Committers may go inactive for a variety of reasons. The
- decision making process of the project relies on active committers who
- respond to discussions and votes in a constructive and timely manner. The PMC
- is responsible for ensuring the smooth operation of the project. A Committer
- that is disruptive, does not participate actively, or has been inactive for
- an extended period may have his or her commit status removed by the PMC.</p>
- <p>Active participation in the user newsgroup and the appropriate developer
- mailing lists is a responsibility of all Committers, and is critical to the
- success of the project. Committers are required to monitor and contribute to
- the user newsgroup.</p>
- <p>Committers are required to monitor the developer mailing list associated
- with all subprojects and components for which they have commit privileges.
- This is a condition of being granted commit rights to the subproject or
- component. It is mandatory because committers must participate in votes
- (which in some cases require a certain minimum number of votes) and must
- respond to the mailing list in a timely fashion in order to facilitate the
- smooth operation of the project. When a Committer is granted commit rights
- they will be added to the appropriate mailing lists. A Committer must not be
- unsubscribed from a developer mailing list unless their associated commit
- privileges are also removed.</p>
- <p>Committers are required to track, participate in, and vote on, relevant
- discussions in their associated subprojects and components. There are three
- voting responses: +1 (yes), -1 (no, or veto), and 0 (abstain).</p>
- <p>Committers are responsible for proactively reporting problems in the bug
- tracking system, and annotating problem reports with status information,
- explanations, clarifications, or requests for more information from the submitter.
- Committers are responsible for updating problem reports when they have done
- work related to the problem.</p>
- <p><b>Subprojects</b><br>
- The work of the Project is organized into subprojects. New subprojects must
- be significant works consistent with the mission of the Eclipse Project, be
- recommended by the PMC, and confirmed by the Board. Subprojects can be
- discontinued by decision of the Board.</p>
- <p>When a new subproject is created, the PMC appoints a subproject lead to
- act as the technical leader and names the initial set of Committers for the
- subproject. Thereafter the PMC may appoint a new subproject lead from time to
- time as required, but the new subproject lead must be confirmed by a majority
- of the other Committers of the subproject. Subproject leads are accountable to
- the PMC for the success of their project.</p>
- <p><b>Subproject Components</b><br>
- The PMC may decide to divide subproject further into components. If a
- subproject is divided into components, commit privileges are normally granted
- at the component level, and the committers for a given component vote on
- issues specific to that component. Components are established and
- discontinued by the PMC. When the PMC creates a component it appoints a
- component lead to act as the technical leader and names the initial set of
- Committers for the component. The component lead is designated as a committer
- for the subproject and represents the component in discussions and votes
- pertaining to the subproject as a whole. Component Committers do not
- participate in votes at the level of the subproject as a whole, unless they
- are also the component lead.</p>
- <p><b>Ports</b><br>
- For components that contain platform-specific code (such as SWT), it may be
- advantageous to allow developers to work on a port of the component to a new
- platform without requiring that they already be committers for the component.
- In this case the main code base is known as the component "core",
- and the port code base is known as a component "port". The decision
- to set up a port is made by the PMC. When a new port of a component is
- created, the PMC appoints a Port Lead, and an initial set of committers who
- will have commit and voting privileges specifically for the port. The port is
- done under the auspices of the core component, and all committers for the
- core component automatically also have commit and voting privileges on the
- port. Normally the Component Lead will also be the Port Lead.</p>
- <p><b>Architecture Team</b><br>
- The Platform, JDT, and PDE will have coordinated release plans, milestone
- dates, freeze cycles, builds, and ship dates. These subprojects will be
- coordinated by a group consisting of the subproject leads, the component
- leads from these subprojects, and the members of the PMC. This group will be
- called the Eclipse Project Architecture Team.</p>
- <p><b>Infrastructure</b><br>
- The infrastructure required to support the development process is the
- responsibility of the PMC. The Eclipse Project will have at least the
- following:</p>
- <ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Bug Database - Bugzilla
- database for tracking bugs and feature requests. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Source Repository -- One or
- more CVS repositories containing both the master source code and
- documentation for the subprojects. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Website - A website will
- contain information about the project, including documentation,
- downloads of releases, and this charter. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>General Mailing List -
- Mailing list for development discussions pertaining to the project as a
- whole or that cross subprojects. This mailing list is open to the
- public. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Subproject Mailing Lists -
- Development mailing list for technical discussions related to the
- subproject. This mailing list is open to the public. <o:p></o:p></span></li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
- auto;mso-list:l2 level1 lfo3;tab-stops:list .5in'><span
- style='font-size:10.0pt;font-family:Arial'>Component Mailing Lists --
- Development mailing list for technical discussions related to the
- component. This mailing list is open to the public. <o:p></o:p></span></li>
- </ul>
- <p><b>The Development Process</b><br>
- Each subproject lead must produce a development plan for the release cycle,
- and the development plan must be approved by the PMC and by a majority of
- Committers of the subproject.</p>
- <p>Each subproject must identify, and make available on its web site, the
- requirements and prioritizations it is working against in the current release
- cycle. In addition, each subproject must post a release plan showing the date
- and content of the next major release, including any major milestones, and
- must keep this plan up to date.</p>
- <p>The Committers of a subproject or component decide which changes may be
- committed to the master code base of a subproject or component respectively.
- Three +1 ('yes' votes) with no -1 ('no' votes or vetoes) are needed to
- approve a code change. Vetoes must be followed by an explanation for the veto
- within 24 hours or the veto becomes invalid. All votes are conducted via the
- developer mailing list associated with the subproject or component.</p>
- <p>Special rules may be established for subprojects or components with fewer
- than three Committers. For efficiency, some code changes from some
- contributors (e.g. feature additions, bug fixes) may be approved in advance,
- or approved in principle based on an outline of the work, in which case they
- may be committed first and changed as needed, with conflicts resolved by
- majority vote of the Committers of the subproject or component, as
- applicable. More restrictive rules for releasing changes may be established
- by the PMC near the end of release cycles or for maintenance streams.</p>
- <p>The master copy of the code base must reside on the project web site where
- it is accessible to all developers and committers. Committers must check
- their changes and new work into the master code base as promptly as possible
- (subject to any check-in voting rules that may be in effect) in order to
- foster collaboration among widely distributed groups and so that the latest
- work is always available to everyone. The PMC is responsible for establishing
- a release engineering and build process to ensure that builds can be reliably
- produced on a regular and frequent basis from the master code base and made
- available for download from the project web site.</p>
- <p>The PMC is responsible for establishing the level of testing appropriate
- for each subproject, and approving the test plans.</p>
- <p>All development technical discussions are conducted using the development
- mailing lists. If discussions are held offline, then a summary must be posted
- to the mailing list to keep the other committers informed.</p>
- <p><b>Licensing</b><br>
- All contributions to the Eclipse Project must adhere to the Common Public
- License <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
- Notwithstanding the above, at the discretion of the PMC, Eclipse Project
- downloads may include separately licensed code from third parties as
- a convenience and where permitted by the third party license, provided
- this is clearly indicated.</p>
- <p>All contributions must contain the following copyright notice.</p>
- <pre>/**********************************************************************</pre>
- <pre>Copyright (c) {date} {name of original contributor} and others.</pre>
- <pre>All rights reserved. This program and the accompanying materials</pre>
- <pre>are made available under the terms of the Common Public License v1.0</pre>
- <pre>which accompanies this distribution, and is available at</pre>
- <pre><a
- href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a></pre>
- <pre><![if !supportEmptyParas]> <![endif]><o:p></o:p></pre><pre>Contributors:</pre><pre><span style="mso-spacerun: yes"> </span><contributor1> - <description of contribution></pre><pre><span style="mso-spacerun: yes"> </span><contributor2> - <description of contribution></pre><pre><span style="mso-spacerun: yes"> </span><span style="mso-spacerun: yes"> </span>...</pre><pre>**********************************************************************/</pre>
- <p> The original contributor is the one who contributes the first version
- of the file. A contributor may be a person or an organization - whoever
- owns the copyright. If the contributor is an organization, the person
- may also be indicated. For each additional contributor, indicate the
- part of the code or contribution that came from the contributor, especially
- if it contains an interesting algorithm or data table etc. For clarity,
- also indicate the contributor in the actual section of contributed code.
- Also reference the bugzilla bug ID if applicable. The basic principle
- is to clearly identify the contribution... especially if it is a separable
- block of code.</p>
- </td>
- <td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'>
- <p class=MsoNormal><![if !supportEmptyParas]> <![endif]><span
- style='font-size:10.0pt'><o:p></o:p></span></p>
- </td>
- </tr>
-</table>
-
-<p class=MsoNormal style='margin-top:14.2pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></p>
-
-</div>
-
-</body>
-
-</html>
diff --git a/eclipse-charter.html b/eclipse-charter.html
deleted file mode 100644
index 18da45b..0000000
--- a/eclipse-charter.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<html>
- <head>
- <meta http-equiv="refresh" content="2; url=eclipse-charter.php" />
- </head>
- <body>
- <a href="eclipse-charter.php">This page has moved. Please update your links and bookmarks.</a>
- </body>
-</html>
\ No newline at end of file
diff --git a/eclipse_project_plan_2_0_rev0214.html b/eclipse_project_plan_2_0_rev0214.html
deleted file mode 100644
index a54b643..0000000
--- a/eclipse_project_plan_2_0_rev0214.html
+++ /dev/null
@@ -1,1359 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-
-<html>
-
-<head>
-
- <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-
- <meta name="Author" content="Eclipse Project PMC">
-
- <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-
- <meta name="ProgId" content="FrontPage.Editor.Document">
-
- <title>Eclipse Project 2.0 Plan</title>
-
- <link rel="stylesheet" href="../default_style.css" type="text/css">
-
-</head>
-
-<body>
-
-
-
-<h1>
-
-Eclipse Project<br>
-
-DRAFT 2.0 Plan</h1>
-
-Last revised Wednesday, February 14, 2002 [<u><font color="#008000">noting changes
-since previous draft plan Friday, December 21, 2001</font></u>]
-<p><i> Please send comments about this draft plan to the </i><a href="mailto:eclipse-dev@eclipse.org">eclipse-dev@eclipse.org</a>
-<i>developer mailing list.</i></p>
-
-<p>This document lays out the plan for the next major release of the Eclipse Project,
- designated release 2.0. The main emphasis of the Eclipse Project 2.0 release
- will be on improving quality (bug fixing) and performance, with a lesser emphasis
- on adding new features and APIs.
-<p>This plan serves at least two purposes. First, it serves as the blueprint guiding
- the efforts of the developers working on the Eclipse Project subprojects. The
- work items committed in this plan were selected over all others because they
- were judged to provide the most value to customers for this follow-on to the
- Eclipse Project 1.0 release. Second, this plan serves as an important input
- to the planning processes of the various customers of the Eclipse Platform.
- This plan tells them what to expect (or what not to expect) in the next release
- so that they can plan their projects accordingly.
-<p>Plans are rarely completely unchanging over the life cycle of a release, and
- this project is no exception. We will update this document as required to reflect
- any changes to the 2.0 release plan. While we certainly do not expect to backtrack
- on items already committed, we do anticipate adding further committed items
- to the list. This plan already includes a number of extra work items which we
- are presently unable to commit to for the 2.0 release due to time, but which
- are nonetheless worthy of being solved. Where possible, we will try to complete
- these items, and will revise this plan as soon as we know we can make a definite
- commitment. The individual Eclipse Project <a href="http://www.eclipse.org/eclipse/index.html" target="_top">subproject
- and component web pages</a> and <a href="http://www.eclipse.org/mail/index.html" target="_top">developer
- mailing list archives</a> contain further, in-depth information about how a
- component is changing. Particular problem reports being worked on for the 2.0
- release can be tracked through the <a href="http://dev.eclipse.org/bugs/">bug
- database</a>; the "Target Milestone" field reflects when a work item
- will become available in the main development stream.
-<p>[<font color="#008000"><u>This draft plan has changed significantly over the
- previous draft dated December 21, 2001. The Eclipse SDK user community has told
- us that they want to see additional improvements in certain areas, and that
- an early release that did not address their needs would be less interesting,
- and would only delay the availability of the follow-on release that did address
- their concerns. We therefore extended the development schedule to include a
- number of new committed items, many of which were previously known but on the
- uncommitted list. In addition, we deleted a few uncommitted items that we know
- will not be done in the Eclipse Project 2.0 release, and revised several items
- to more accurately describe what we will be doing. We added 3 more milestones
- (M4, M5, M6), and are now targeting May 2002 for the Eclipse Project 2.0 release,
- rather than April.</u></font>]
-<h2>Release deliverables</h2>
-
-<p>The release deliverables are:
-
-<ul>
-
- <li>Source code release for Eclipse Project, available as versions tagged "R2_0"
- in the Eclipse Project <a href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.</li>
-
- <li>Eclipse Project SDK (includes Platform, JDT, and PDE source zips)
-
- (downloadable).</li>
-
- <li>Eclipse Platform runtime binary distribution (downloadable).</li>
-
- <li>JDT runtime binary distribution (downloadable).</li>
-
- <li>Eclipse SDK Examples (downloadable).</li>
-
-</ul>
-
-<h2>Release milestones</h2>
-
-<p>The release milestones are:</p>
-
-<ul>
-
- <li>December 7, 2001 - milestone 0 - stable build reflecting progress</li>
-
- <li>December 21, 2001 - milestone 1 - stable build reflecting good progress</li>
-
- <li>January 25, 2002 - milestone 2 - stable build reflecting significant
-
- progress</li>
-
- <li>February 15, 2002 - milestone 3 - stable build reflecting significant
-
- progress [<u><font color="#008000">former initial development freeze</font></u>]</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] March 15, 2002 -
- milestone 4 - stable build reflecting significant
-
- progress</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] April 5, 2002 - milestone
- 5 - stable build reflecting significant
-
- progress</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] April 26, 2002 - milestone
- 6 - stable build - feature complete -
-
- initial development freeze</li>
-
-</ul>
-
-<p>
-
-The 2.0 release is targeted for May 2002 [<u><font color="#008000">formerly
-April</font></u>]. All release deliverables will be available for download
-
-as soon as the release has been tested and validated in the target operating
-
-configurations listed below.</p>
-
-<h2>
-
-Target Operating Environments</h2>
-
-
-
-<p>Most of the Eclipse SDK is "pure" Java and has no direct dependence on the
- underlying operating system. The chief dependence is therefore on the Java 2
- Platform itself. The 2.0 release of the Eclipse Project will be written against
- version 1.3 of the Java 2 Platform APIs, and targeted to run on either version
- 1.3 or 1.4 of the Java 2 Runtime Environment, Standard Edition.</p>
-
-<p>We plan to test and validate the Eclipse SDK 2.0 on the most up-to-date Java
- 2 Platform implementations available. These are:</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="19%"><b>Operating system</b></td>
-
- <td width="24%"><b>Processor architecture</b></td>
-
- <td width="73%"><b>Java 2 Platforms</b></td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Microsoft<br>
-
- Windows</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for
-
- Microsoft Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Windows, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Microsoft
- Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Linux</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Linux, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="2">Sun Solaris</td>
-
- <td width="24%" rowspan="2">SPARC</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Solaris
-
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Solaris
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="19%">HP HP-UX</td>
-
- <td width="24%">hp9000 PA-RISC</td>
-
- <td width="73%"><span class="header">HP-UX SDK for the Java 2 platform,
-
- version 1.3.1 for hp9000 PA-RISC</span></td>
-
- </tr>
-
- <tr>
-
- <td width="19%">IBM AIX</td>
-
- <td width="24%">PowerPC</td>
-
- <td width="73%">IBM Developer Kit for AIX, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
-</table>
-
-<p><span class="header">The following table describes the combinations of operating
- system and Java 2 Platform used when testing the Eclipse SDK configurations.
- The status column indicates the level of testing: Primary means a full tested
- configuration; </span>Secondary means a configuration which is only lightly
- tested; Untested means a configuration that has received no testing, but which
- should work. Note that the Linux GTK configuration is considered early access
- for the 2.0 release; it will be tested, but it is known in advance that it will
- not be of product quality in this release.</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="11%"><b>Window system</b></td>
-
- <td width="28%"><b>Java 2 Platform<br>
-
- (see above table)</b></td>
-
- <td width="42%"><b>Operating Environment</b></td>
-
- <td width="19%"><b>Testing Status</b></td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="5">Win32</td>
-
- <td width="28%" rowspan="5">Windows on Intel x86</td>
-
- <td width="42%">Windows 2000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows XP</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows ME</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows 98SE</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows NT</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="6">Motif</td>
-
- <td width="28%" rowspan="3">
-
- <p>Linux on Intel x86</p>
-
- <p> </td>
-
- <td width="42%">RedHat Linux 7.2 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">
-
-SuSE Linux 7.3 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and XFree86 version 4.1.0</td>
-
- <td width="19%">Untested</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">Solaris on SPARC </td>
-
- <td width="42%">Sun Solaris 8 SPARC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">HP-UX on hp9000 PA-RISC</td>
-
- <td width="42%">HP-UX 11i hp9000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">AIX on PowerPC</td>
-
- <td width="42%">IBM
-
-AIX 5.1 on PowerPC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="3">GTK</td>
-
- <td width="28%" rowspan="3">Linux on Intel x86</td>
-
- <td width="42%">RedHat Linux 7.2 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%"> SuSE Linux 7.3 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and GTK 2.0</td>
-
- <td width="19%"><i>Early access; untested</i></td>
-
- </tr>
-
-</table>
-
-<h4>
-
-Internationalization</h4>
-
-<p> The Eclipse Platform 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.</p>
-
-
-
-<p>Latin-1 locales will be supported by the Eclipse SDK on all of the above operating
- environments; DBCS and BIDI locales will be supported by the Eclipse SDK only
- on Windows operating environments. [<font color="#008000"><u>In the previous
- draft, internationalization was planned only for Windows operating environments.</u></font>]
-<p>The Eclipse SDK will support the GB 18030, the new Chinese code page standard,
- on Windows 2000 and XP only. Note that GB 18030 also requires locale and character
- encoding support from the Java 2 Runtime Environment; this support is standard
- in version 1.4, and also available in some 1.3 JREs.
-<p>We will perform tests in German and Japanese locales.
-
-<h4>
-
-BIDI support</h4>
-
-<p> The Eclipse SDK 2.0 is a development environment targeted at technical professionals
- - not an end user application. However the Eclipse SDK 2.0 tools will permit
- technical professionals who are working in English to build Hebrew/Arabic end
- user Java programs which are themselves not based on the Eclipse SDK. The BIDI
- support in the Eclipse SDK 2.0 allows a Java programmer to work with BIDI strings,
- code comments, etc but the Eclipse SDK itself is not designed to be localized
- for BIDI locales and its widget orientation can not be changed.</p>
-
-<p>IMPORTANT: The above BIDI support is available only on Windows platforms.</p>
-
-<h2>
-
-Compatibility with Previous Release</h2>
-
-The Eclipse SDK 2.0 will be upwards compatible with the Eclipse SDK 1.0 to the
-greatest extent possible. We anticipate a small number of areas where slavishly
-maintaining compatibility would not be in the best interests of the Platform or
-its clients. All such exceptions will be noted in the 2.0 release notes so that
-clients can assess the impact of these changes on their plug-ins and products.
-<p><b>Status of interim 1.0 APIs and plug-ins</b>: Some of the Eclipse SDK APIs
- and plug-ins in 1.0 were marked as provisional (debug, for instance). These
- APIs and plug-ins will either appear in stable, finished form in the 2.0 release,
- or be removed. As anticipated (and advertised), these API changes will likely
- break 1.0 client plug-ins that made use of that particular API in its early
- form. Even if code appears to work with 2.0, it would still need to be completely
- reviewed to ensure that it abides by the final API contracts.</p>
-
-<p><b>API Contract Compatibility:</b> The Eclipse SDK 2.0 will be upwards contract-compatible
- with the Eclipse SDK 1.0 unless noted. This means that programs in full compliance
- with contracts specified in the Eclipse SDK 1.0 APIs will automatically be in
- full compliance with the Eclipse SDK 2.0 APIs. (API is construed broadly to
- include such things as plug-in extension points.) Downward contract compatibility
- is not supported. There is no guarantee that compliance with the Eclipse SDK
- 2.0 APIs would ensure compliance with the Eclipse SDK 1.0 APIs.
-<p><b>Binary (plug-in) Compatibility:</b> The Eclipse SDK 2.0 will be upwards
- binary-compatible with the Eclipse SDK 1.0 unless noted. This means that plug-ins
- built for the Eclipse SDK 1.0 will continue to work correctly in the Eclipse
- SDK 2.0 without change. Downward plug-in compatibility is not supported. Plug-ins
- for the Eclipse SDK 2.0 are unlikely to be usable in the Eclipse SDK 1.0. Plug-ins
- with hard-coded references in their plug-in manifest file to 1.0 versions of
- prerequisite Eclipse Project plug-ins will not work in 2.0 as the plug-in version
- numbers will be incompatible.
-<p><b>Source Compatibility:</b> The Eclipse SDK 2.0 will be upwards source-compatible
- with the Eclipse SDK 1.0 unless noted. This means that source files written
- to use the Eclipse SDK 1.0 APIs can be successfully compiled and run against
- the Eclipse SDK 2.0 APIs. Since source incompatibilities are easy to deal with,
- maintaining source compatibility is considered much less important than maintaining
- contract and binary compatibility. Downward source compatibility is not supported.
- If source files use new Eclipse SDK APIs, they will not be usable with an earlier
- version of the Eclipse SDK.
-<p><b>Workspace Compatibility:</b> Eclipse SDK 2.0 will be upwards
-
-workspace-compatible with Eclipse SDK 1.0 unless noted. This means that
-
-workspaces and projects created with Eclipse SDK 1.0 can be successfully opened by Eclipse SDK
-
-2.0 and upgraded to a 2.0 workspace. Individual plug-ins developed for
-
-Eclipse SDK 1.0 should provide similar upwards compatibility for their workspace
-
-metadata; plug-in developers are responsible for ensuring that their plug-ins
-
-recognize 1.0 metadata and process it appropriately. Note: the interim
-
-Eclipse SDK 1.0 plug-ins (ones with provisional APIs) are unlikely to automatically
-
-upgrade their metadata to 2.0. User interface session state may be discarded
-when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created
-
-(or opened) by Eclipse SDK 2.0 will be unusable with an earlier version
-
-of Eclipse SDK.
-
-<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and certainly
- everything in a package with "internal" in its name, are considered
- implementation details which may vary between operating environment and are
- subject to change without notice. Client plug-ins that directly depend on anything
- other than what is specified in the Eclipse SDK API are inherently unsupportable
- and receive no guarantees about compatibility within a single release much less
- with an earlier release. Refer to <i><a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
- to Use the Eclipse API</a></i> for information about how to write compliant
- plug-ins.
-<h2> Eclipse Project Subprojects</h2>
-
-The Eclipse Project consists of 3 subprojects. Each subproject
-
-is covered in its own section:
-
-<blockquote><font size=+0><a href="#Eclipse Platform subproject">Eclipse Platform</a></font>
-
-<br><font size=+0><a href="#Java development tooling (JDT) subproject">JDT - Java development tooling</a></font>
-
-<br><font size=+0><a href="#Plug-in development environment (PDE) subproject">PDE - Plug-in development environment</a></font></blockquote>
-
-<p>For each subproject, the items listed reflect new features of the Eclipse Platform,
- or areas where existing features will be significantly reworked. Each item indicates
- the component affected by that work item (many items involve coordinated changes
- to several components).
-<p>Note that fixing bugs, improving test coverage, documentation, examples,
-
-etc. are considered routine ongoing maintenance activities and are not
-
-included in this plan unless they would also involve significant changes to the Platform.
-
-<h3>
-
-<a name="Eclipse Platform subproject">Eclipse Platform subproject</a></h3>
-
-The following items reflect new features of the Eclipse Platform, or areas
-
-where existing features will be significantly reworked. Each item indicates
-
-the component affected by that work item (some items involve coordinated
-
-changes to several components). Additional uncommitted items affecting these
-
-components are listed in the <a href="#Uncommitted Items">Uncommitted Items</a>
-
-section at the end.
-
-<h4>
-
-Platform Core component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform
-
-Core component</a> covers most of the Platform's non-UI infrastructure,
-
-including the basic plug-in mechanism, resources in the workspace. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve Platform startup times">Improve Platform
-
-startup times</a>.</b> Eclipse Platform startup times 1.0 reflect the speed of XML parsing for plug-in manifest files. As the sheer number of available
-
-plug-ins can be expected to increase by an order of magnitude in the near future,
-
-we need a more scalable solution to this problem. An improvement in startup
-
-time will come with computing and caching the plug-in registry on disk.
- <p>[<u><font color="#008000">Replacement item</font></u>] <b><a name="Improve Ant integration and the build story">Improve
- Ant integration and the build story</a>.</b> In 1.0, Ant is not as well integrated
- into the workbench as it could be. In 2.0, we plan to make it more convenient
- to run Ant scripts from the Workbench, including ones not originally written
- for use inside the platform. We also plan to make the platform's build story
- more transparent, and allow Ant steps to be included. These changes impact
- the UI component as well. [formerly called <a name="Improve Ant integration"><b>Provide
- first-class Ant integration</b></a><b>]</b>
- <p><a name="Improve serviceability"><b>Improve serviceability</b></a><b>.</b>
-
-Several factors make it difficult in 1.0 to debug an Eclipse Platform that
-
-is failing in the field: startup failures are poorly diagnosed; error messages in the log sometimes contain little
-
-or no useful information; the internal plug-in log file is busy while the
-
-Platform is running, and gets erased as soon as the Platform is restarted.
-
-We plan to improve the startup sequence, eliminate unhelpful error messages, take steps to help identify
-
-which plug-in is the apparent source of an internal error, and ensure that
-
-the information in the internal logs is more readily accessible. These changes will
-
-also impact the UI component.<p>[<font color="#008000"><u>Replacement
- for previously uncommitted item</u></font>] <b><a name="Allow VCM control over rename/move/delete">Allow VCM control over
- rename/move/delete</a>.</b> VCM providers sometimes need tighter control over how project resources are manipulated in the local file system. For instance, a project directory might be a specially mounted remote file system located on a VCM server, and require special server communication in order to delete, move, or change the name of a resource. Or the VCM provider may track version history across move/renames. (Other clients would like a similar opportunity to veto inappropriate name changes to their resources; this is a different concern.) We will add a headless callback so that the relevant VCM provider will be able to control moves, renames, and deletes. These changes will affect the VCM
- component as well.
-
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Support unmanaged resources in managed projects"><b>Support
-
-unmanaged resources in managed projects</b></a><b>.</b> Workspace projects often contain
-
-files derived by processing other files; it is usually the case that these
-
-derived files should not be under VCM, even though the rest of the files
-
-in the project are. Workspace projects may also contain extra files or
- directories in which the VCM provider stores metadata; however, these files
- are not of direct interest to either the user or to regular plug-ins. There needs to be some means of dealing with
- these;
-
-depending on the solution, this may require support from the UI as well as Core.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve support for product branding">Improve
- support for product branding</a>.</b> We will make it easier to furnish custom product
- information such as splash screens, product startup configuration, distinctive icons for
- product branding, product-specific preference settings, etc.</blockquote>
-
-
-
-<h4>
-
-Installation and Update component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html"> Installation and Update component</a> is responsible for installing and upgrading the Eclipse
-
-Platform in the field. Eclipse SDK 1.0 contains an early version
-
-of this component; it will be thoroughly reworked for 2.0. The following items
-
-are committed for 2.0:
-
-<blockquote>
-
- <p><b><a name="Redesign plug-in install and update story">Redesign
-
-plug-in installation and update story</a>.</b> The 1.0 concepts of <i>component</i>
-
- and <i>configuration</i> will be replaced with a new concept called a <i>feature</i>.
-
- Features define the packaging structure for a group of related plug-ins,
-
- plug-in fragments, and optionally non-plug-in files. This change impacts the Core
-
-component and the PDE subproject as well.</p>
-
- <p><b><a name="Improve installer flexiblilty">Improve installer </a><a name="Improve installer flexiblilty">flexibility</a>.</b>
-
- The standard Platform installer will be more flexible and support alternate
-
- packaging and site management schemes: structured site map for discovering
-
- available updates; improved granularity of downloads; accommodate native
-
- installers; feature-specific custom installers packaged with feature and
-
- executed during feature installation.</p>
-
-</blockquote>
-
-
-
-<h4>
-
-Platform UI component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html">Platform
-
-UI component</a> provides the generic workbench UI for the Eclipse Platform. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve accessibility - UI">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required to meet minimum
-
- accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The workbench and its standard views and wizards must meet minimum
-
- accessibility guidelines, including mouse-less operation. The Eclipse Platform
-
- needs to enable other client plug-ins to meet accessibility guidelines too.
-
- This change also impacts the SWT component.
-
- <p><b><a NAME="Improve editor management">Improve editor management</a>.</b>
-
-Users are finding it difficult to work with many editors open simultaneously
-
-in the Eclipse SDK 1.0 workbench, all seemingly stemming from the way editors
-
-are currently managed. The workbench's approach to editor management will
-
-be reviewed and revised to improve usability.
-
-<p><b><a name="Improve interaction between editors and views">Improve
-
-interaction between editors and views</a>.</b> There are some unfortunate interactions
-
-between editors and views in Eclipse SDK 1.0 that make it difficult for views
-
-to serve as "secondary windows" to an editor. Among other things, this
-
-leads to poor integration of standard views. The workbench's current approach
-
-to editors and views will be reviewed and revised to facilitate interaction
-
-and improve integration.
-
-<p><b><a name="Allow context menu contributions in Outline view">Allow
-
-context menu contributions in Outline view</a>.</b> In Eclipse SDK 1.0, clients
-
-have no control over the standard Outline view's popup context menu. This
-
-will be addressed so that clients will be able to make contributions to
-
-this menu.
-
-<p><b><a name="Improve usability re: losing context">Improve usability
-
-re: losing context</a>.</b> Some users have reported getting lost in the UI
-
-and having to close all open editors and perspectives to get their workbench
-
-back into a familiar state. The current approach will be reviewed and revised
-
-to improve usability.
-
-<p><b><a name="Improve the Task view">Improve the Task view</a>.</b> The
-
-standard Task view will be improved in the following areas: performance and
-
-usability for large numbers of items in the view; context-sensitive help; and
-
-making contributions to the view's context menu.<p><b><a name="Add support for working sets">Add support for working
-
- sets</a>.</b> In 1.0, all resources in the workspace are equally accessible.
-
- The workbench will let the user define working sets of resources, suitable for
-
- providing more restricted contexts for browsing, searching, and the like.
-
-<p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Improve usability of project natures"><b>Improve
-
-usability of project natures</b></a><b>.</b> In Eclipse SDK 1.0, project natures are secretly
-
-configured by the plug-ins that define them, leading to problems and blind
-
-spots when projects have other natures as well. We will enrich the underlying
-support for natures by adding declarative constraints between natures, and
-expose them to the user in the form of "capabilities" which the user
-may (re-)configure their project with. These
-
-changes also affect the Core component.
-
-<p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve consistency of saving workbench state"><b>Improve
-
-consistency of saving workbench state</b></a><b>.</b> In Eclipse SDK 1.0, there are a
-
-number of instances where user-configurable UI settings are not being persisted
-
-between sessions. The UI will provide better support for saving important
-
-UI state.
-
- <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Improve support for file encodings">Improve support for file encodings</a>.</b>
- Editors and other tools need to have the correct file encoding in order to
- read or write text files. In Eclipse SDK 1.0, everything uses the default file
- encoding for the current locale. We will improve this for Eclipse SDK 2.0.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Improve support for clipboard-based cut/copy/paste">Improve
- support for clipboard-based cut/copy/paste</a>.</b> There are several places in the
- workbench where cut/copy/paste are not enabled where
- they should be. The UI will allow clients to supply these actions so they work
- as expected.</blockquote>
-
-
-
-<h4>
-
-SWT component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html">SWT
-component</a> is the low-level widget toolkit used in the Eclipse Platform. The
-following items are committed for 2.0:
-<blockquote>
-
- <p><b><a name="Port to other window systems">Support additional window
-
- systems</a>.</b> Add support for new window system: GTK. Port Motif-based
-
- implementation to other operating systems: AIX, HP-UX, Solaris. Foster and
-
- encourage efforts to port to other window systems.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Support GB18030"><b>Support
- GB18030</b></a><b>.</b> GB 18030 is a new Chinese code page standard. Products
- shipping into the China market are required to support this new standard.
- The GB 18030 character encoding support is standard in Java 2 Runtime Environment
- version 1.4, and also available in some 1.3 JREs.
- <p><b><a name="Utilize native Unicode support">Utilize
-
- Windows native Unicode support</a>.</b> The SWT implementation will use
-
- native Unicode support on all Windows operating systems that support it (NT,
-
- 2000, XP).<p><b>Improve Motif appearance and performance.</b> In 1.0,
-
- support for the Motif window system lags behind that of Windows. We plan to improve the
-
- appearance and performance of SWT on Motif.
- <p><font FACE="Times New Roman" COLOR="#000000">[</font><u><font FACE="Times New Roman" COLOR="#008000">New
- item</font></u><font FACE="Times New Roman" COLOR="#000000">] <b>Remove
- internal call to XinitThreads</b>. In 1.0 on Motif, the internal call that SWT
- makes on XinitThreads prevents drag and drop, and printing from working. In
- 2.0, we will find a way to remove this impediment.</font></p>
-
-</blockquote>
-
-
-
-<h4>
-
-VCM component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> VCM component</a> provides version and configuration management for projects
-
-in the workspace and attendant team support. The following items are committed for 2.0:
-
-<blockquote><a name="Provide VCM API"><b>Provide an open VCM </b></a><b><a name="Provide VCM API">story</a>.</b> Eclipse SDK
-
-1.0 includes CVS repository support, but has no official VCM API that allows
-
-other version and configuration management systems to integrate into the
-
-Platform. We will provide a simple API, extension points, and usage guidelines
-
-so that VCM providers can adapt their repositories and integrate VCM product-specific
-
-UI elements into the Eclipse SDK UI.
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve CVS repository integration"><b>Improve
- CVS repository integration</b></a><b>.</b> In addition to converting the existing
- CVS repository adapter to the new VCM API, CVS support will be improved, including:
- support for CVS modules so that the platform can be connected to existing
- CVS repositories; support for CVS patch facility so that CVS users can capture
- changes to a project in a tangible form that can be submitted to others or
- archived (this also involves the compare infrastructure); correct classification
- of text and binary files.
-</blockquote>
-
-
-
-<ul><a name="Add mechanism for validating edits and saves"><b>Add mechanism
-
-for validating edits and saves</b></a><b>.</b> Some VCM providers require a "heads up" when the user starts
-
-to change the contents of a file open in an editor (e.g., to allow the file to
-
- be checked out and locked), or when the user is about to save the changed contents
-
-back to disk. We will add a callback so that the relevant VCM provider will be
-
- able to register for advance notification with an opportunity to veto. This
-
- change also affects the UI and Core components.<p> <b><a name="Add non-versioning WebDAV repository support">Add non-versioning
- WebDAV repository
- support</a>.</b>
-
- We plan to build a simple repository adapter for non-versioning WebDAV
- servers. This will allow users to share their files via any WebDAV compliant
- server. This also affects the Core component (target management API).</p>
-
-</ul>
-
-
-
-<h4>
-
-Help component</h4>
-
-
-
-<p>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html"> Help component</a> organizes help contributions and presents them to the
-
-user. The following items are committed for 2.0:</p>
-
-<blockquote><p><b><a name="Simplify contribution mechanism">Simplify
-
- contribution mechanism</a>.</b> Based on feedback on 1.0, we plan to rework
-
- and simplify the help contribution mechanism. Online documentation created for 1.0 will
-
- need to be converted for 2.0.<p>[<u><font color="#008000">Revised
- item</font></u>] <a name="Use a separate web browser to present help"><b>Use
-
-a separate web browser to present help</b></a><b>.</b> We will use an external
-
- web browser launched in a separate window to present all documentation and online help. This will allow help to be presented in a non-modal way.
- We will support one help browser for each target environment. Refer to the
- <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/eclipse_project_plan_2_0_supported_browsers.html">table</a>
- in the Help Component for additional information on supported browsers.
- <p><b><a name="Support live help">Support live help</a>.</b> We will support
- the ability to trigger developer-supplied actions as a result of navigating
- a link in the online documentation. The actions will execute within the Eclipse
- Platform environment.
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow remote help content">Enable
- help server</a>s.</b> It is often desirable to be able to make plug-in documentation
- accessible to users that do not have the Eclipse Platform installed. We will
- support configurations where online documentation can be hosted on a web server
- and viewed through a regular web browser. [<u><font color="#008000">The former
- "Info Center" item has been merged with this one.</font></u>]
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support standalone help">Support
- standalone help</a>.</b> Developers will be able to reuse the Eclipse Platform
- help function even in products that are not built using the Eclipse Platform
- itself.
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>]
- <a name="Add help search support"><b>Add help search support</b></a><b>.</b>
-
- We will provide the ability to search help documentation, based on <a href="http://jakarta.apache.org/lucene/docs/index.html">Lucene</a>.
- Stemmers will be used when available for the language; for example, the Porter
- stemming algorithm is used for English.
-
-</blockquote>
-
-
-
-<h4>
-
-Platform Debug component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html">Platform
-
-Debug component</a> provides generic Core and UI for launching, running, and debugging
-
-programs. The following items are committed for 2.0:
-
-<blockquote><a name="Stabilize Debug API"><b>Stabilize Debug API</b></a><b>.</b>
-
-In Eclipse SDK 1.0, all debug APIs were considered provisional and incomplete.
-
-The Debug APIs will appear in finished, stable form.</blockquote>
-
-
-
-<blockquote><a name="Add support for debugging procedural languages"><b>Add
-
-support for debugging procedural languages</b></a><b>.</b> The Debug component will be extended to
-
- enable debuggers to be written for procedural languages (e.g., C) which get compiled to machine code and run
-
-on standard hardware.
-
-<p><a name="Add launch configurations"><b>Add launch configurations</b></a><b>.</b>
-
-The Debug component will add a general mechanism and UI for the user to define launch
-
-configurations describing how something is to be launched (e.g., command
-
-line options).</blockquote>
-
-
-
-<h4>
-
-Scripting component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-scripting-home/main.html">Scripting
-component</a> provides general support for scripting (other than Ant). The following
-item is committed for 2.0:
-
-<blockquote>
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Remove Scripting component">Remove
- Scripting component</a>.</b>
-
-In Eclipse SDK 1.0, the scripting support was provisional and incomplete. It is now
- clear that we will not become real in the 2.0 timeframe. The Scripting
- component will be withdrawn from the Eclipse Platform (it may be
- re-introduced in a later release).</p>
-</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse Platform subproject)</h4>
-
-<p><i>N.B. The following is the list of important Eclipse Platform subproject
- work items which we are presently unable to commit to for the 2.0 release. Wherever
- possible, we will try to complete these items. Depending on how things work
- out, we should be able complete some of them. However, we cannot promise that
- we will complete any of them, and it would be unwise to gamble otherwise. Items
- not completed for 2.0 will carry over to the planning of the next release. We
- will revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-<ul>
- <p> <a name="Add support for non-local files"><b>Add support for non-local files</b></a><b>.</b>
- It is expensive to set up a workspace project containing a large number of
- files that normally reside on remote server or file system. Core has a basic
- mechanism that permits the workspace to contain placeholders for files and
- folders necessarily resident in the local file system. The Core mechanism
- will be augmented so that VCM can use it to hook it to retrieve files from
- a remote server or file system on demand. The UI component is also affected.
- <p> <a name="Improve undo/redo in workbench"><b>Improve undo/redo in workbench</b></a><b>.</b>
- In Eclipse SDK 1.0, undo and redo are poorly supported for workbench actions,
- and it is still far too easy for a user to lose work. We will consider providing
- an undo/redo service that will help decrease the risk of inadvertently losing
- work.
- <p><a name="Provide a standard Console view"><b>Provide a standard Console view</b></a><b>.</b>
- In Eclipse SDK 1.0, there is a proliferation of consoles furnished by clients
- (including JDT, PDE, Ant). The workbench will supply a standard Console view;
- clients will be encouraged to use it instead of providing their own. These
- changes will affect the UI component.
- <p>[<u><font color="#008000">Deleted item</font></u>] <a name="Improve support for cheat sheets"><b>Improve
- support for cheat sheets</b></a><b>.</b> In Eclipse SDK 1.0, the Welcome editor
- is an example of a cheat sheet. A cheat sheet is an instance of a simple kind
- of workflow support. We will continue to evolve the mechanisms behind cheat
- sheets, including adding standard API for creating actions. These changes
- will affect the UI component. [<font color="#008000"><u>This has turned out
- to require a major effort, so we are removing this uncommitted item from the
- 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide project interchange mechanism">Provide
- project interchange mechanism</a>.</b> We will provide a way to export the
- resources in one of more workspace projects to an archive file that it can
- be saved for posterity or imported to another workspace. This affects the
- Core and UI components. [<font color="#008000"><u>A consequence of the
- new VCM story is that we do not need to provide a special mechanism for project
- interchange. Therefore we are removing this uncommitted item from the 2.0
- plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide additional internationalization support">Provide
- additional internationalization support</a>.</b> We will enable the
- Eclipse Platform to provide internationalization support for additional locales
- on some Motif operating environments. This affects the SWT component. [<font color="#008000"><u>We
- have added support for additional locales (see the Internationalization section
- in this plan for more details). This uncommitted item is redundant,
- so we are removing it from the 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve local resource history">Improve
- local resource history</a>.</b> The workspace local resource history mechanism
- keeps recent copies of modified or deleted files in order to help save the
- user from losing data in common situations. In 1.0, many UI actions that the
- user would reasonably expect to grow the history are not doing so, and there
- is no obvious way to recover a saved state of a file once it has been deleted.
- We plan to make the history facility more reliable and helpful for 2.0.
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Add ftp repository support">Add
- ftp repository support</a>.</b> We plan to build a simple repository adapter
- for ftp servers. This also affects the Core component (target management API).</p>
-</ul>
-
-
-
-<p>(End of items for Eclipse Platform subproject.)
-
-
-
-<h3>
-
-<a name="Java development tooling (JDT) subproject">Java development tooling (JDT) subproject</a></h3>
-
-<a href="http://www.eclipse.org/jdt/index.html">
-
-Java development tooling</a> (JDT) implements a Java IDE based on the Eclipse
-
-Platform.
-
-The following committed items reflect new features of JDT, or areas where existing
-
-features will be significantly reworked.
-
-<blockquote><a name="Reduce memory footprint for Java builder"><b>Reduce
-
-memory footprint for Java builder</b></a><b>.</b> The internal data structures of
-
-the Java incremental compilation mechanism is using more memory than necessary
-
-or reasonable. By fundamentally changing the approach to how incremental
-
-builds are done we expect to substantially reduce the memory footprint
-
-without significantly increasing incremental compile times.
-
-<p><b><a name="Improve Java search">Improve Java search</a>.</b> Java reference
-
-searches in Eclipse SDK 1.0 are limited to named types in source files. This
-
-will be addresses so to make it possible to find references in JAR libraries, and to distinguish read and write accesses to fields.
-
- <p><a name="Improve code assist"><b>Improve code assist</b></a><b>.</b> A number
-
-of changes will improve usability of code assist: including method argument
-
-names and types as hints; suggesting variable names; honoring visibility
-
-constraints dictated by the context.
-
-<p><b><a name="Upgrade Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform">Upgrade
-
-Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform</a>.</b>
-
-A new assertion feature was added in 1.4, and there were a few clarifications
-
-in obscure corners of the Java language specification. The Eclipse Java compiler
-
-will be upgraded to support 1.4, but will continue to support 1.3 via an option
-
-setting.
-
-<p><b><a name="Improve build classpath">Improve build classpath</a>.</b>
-
-By adding a mechanism for explicitly exporting libraries on a project's
-
-build classpath to downstream projects, it becomes possible to have a library
-
-project (one with a JAR and no source folder) that can stand in for a project
-
-containing source code. This change enables large scale development where
-
-source code is contained in multiple, related Java projects, by providing
-
-possibilities other than having all the source code projects in the workspace
-
-at all times (expensive to build). Plug-in development is a direct beneficiary.
-
- <p><b><a name="Improve accessibility - JDT">Improve accessibility</a>.</b> Applications
-
- selling to the US Government market are required by law to meet minimum accessibility
-
- guidelines (<a href="http://www.section508.gov/" target="_top">Section 508</a>).
-
- The JDT UI must meet minimum accessibility guidelines, and enable its client
-
- plug-ins to meet accessibility guidelines as well.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve Java editor"><b>Improve Java editor</b></a>. Rework
-
-menu bar contributions and context menu to improve usability; add a template
-
- facility with variable substitution; add navigation to a method's super
-
- implementation; add bracket matching; add error clueing; add line/column
- numbers.
-
-<p><b><a name="Improve refactoring">Improve refactoring</a>.</b>
-
-Implement additional refactorings: extract variable, inline temporary, push-up
-
-field/method, change method signature. Support reference updates in strings and
-
-comments for move/rename refactorings.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Improve refactoring">Improve package
-
-browsing</a></b>: Provide a more package-centric view for browsing. In 1.0, the
-
-Packages view presents packages grouped by their containers. We will continue to
-support the existing container based presentation; in addition, we are exploring
-alternatives. We
-
-will also add
-
-support to show the structure of a compilation unit in the Packages
-
-view.
-
-<p><b><a name="Facilitate string externalization">Facilitate
-
-</a><a name="Facilitate string externalization">string
-
-externalization</a></b><b>.</b> Add a wizard that
-
-allows the user to
-
-externalizing string literals in Java source code into standard Java resource bundles.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow runtime parameters to the configured">Allow runtime
-parameters to the configured</a>.</b> Using the new launch configuration mechanism
-
-provided by the Platform Debug component will allow the working directory, runtime classpath,
-
-boot classpath, extension directories, and other VM-type specific launch
-
-parameters to be configured.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support hot code replace when debugging JDK 1.4 targets">Support
- hot code replace when debugging compliant Java 1.4 targets</a>.</b> JDPA for
- version 1.4 of the Java 2 Platform allow a class to be updated while under
- the control of the debugger. In 1.0, this kind of support was only available
- for IBM J9 targets. The Java debugger will be changed to support both.
- Provide smart drop to frame that only removes affected frames from the stack.
- <p><b><a name="Enable JSP debugging with JPDA">Enable JSP debugging
-
-with JPDA</a>.</b> The Java debugger will enable JSP debugging via a flexible source lookup algorithm and breakpoint setting mechanism.
-
-<p><a name="Add debugger support for step filtering"><b>Add debugger
-
-support for step filtering</b></a><b>.</b> The Java debugger will avoid stepping into
-
-any class mentioned on a user-specified exclusion list.
-
-<p><b><a name="Improve data inspectors">Improve data inspectors</a>.</b> We will
-
-improve support in the debugger for inspecting objects, including running an
-
-object's toString method to obtain a readable string that may be more
-
-meaningful to the user.
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Add API for Java abstract syntax tree"><b>Add
-
-API for Java abstract syntax tree</b></a><b>.</b> In Eclipse SDK 1.0, refactoring uses
-
-compiler internals for parsing and walking the abstract syntax trees (ASTs)
-
-for Java source code. We will add API for creating and manipulating ASTs
-
-that can serve as the basis for other clients like refactoring. </p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <b><a name="Add field watchpoints">Support field
-
- watchpoints</a>.</b> We will add debugger support for field watchpoints.</p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve Java editor"><b>Support editor key bindings</b></a>. Add support for user-configurable key
-
- bindings in the Java editor. This requires changes in the Platform UI
-
- component.<p>[<u><font color="#008000">New item</font></u>] <b><a name="Add support for JUnit">Add
- support for JUnit</a>.</b> We will include special tooling for the popular <a href="http://www.junit.org/">JUnit
- unit test framework</a> to facilitate authoring and running of JUnit test
- cases.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Add support for Javadoc generation">Add support for Javadoc
- generation</a>.</b> We will add an action for generating Javadoc for a Java
- project (note: requires a standard JDK).<p>[<u><font color="#008000">New
- item</font></u>] <b>Improve navigating to Javadoc.</b>
- We will add quick keyboard navigation from names in Java source code to the
- corresponding Javadoc, including the API Javadoc for names declared in
- libraries.</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse JDT subproject)</h4>
-
-<p><i>N.B. The following is the list of important JDT subproject work items
-
-which we are presently unable to commit to for the 2.0 release. Wherever
-
-possible, we will try to complete these items. Depending on how things work out,
-
-we should be able complete some of them. However, we cannot promise that we will
-
-complete any of them, and it would be unwise to gamble otherwise. Items not
-
-completed for 2.0 will carry over to the planning of the next release. We will
-
-revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-
-
-<blockquote>
- <p> <a name="Add conditional breakpoints"><b>Support conditional
-
- breakpoints</b></a><b>.</b> We will add debugger support
-
- for conditional breakpoints
-
-with simple conditions, including simply object identity tests of the form
-
- "this == id" sufficient for object breakpoints.</p>
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse JDT subproject.)
-
-
-
-<h3>
-
-<a name="Plug-in development environment (PDE) subproject">Plug-in development environment (PDE) subproject</a></h3>
-
-The <a href="http://www.eclipse.org/pde/index.html"> plug-in development environment</a>
-(PDE) consists of tools for developing plug-ins for the Eclipse Platform.
-For 2.0, the goal is to maintain the level of PDE support present in 1.0 while
-adding the necessary extensions that allow it to be the tool of choice for self-hosted
-Eclipse Project development. The following items are committed for 2.0:
-<blockquote> <b><a name="Improve accessibility - PDE">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required by law to meet
-
- minimum accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The PDE UI must meet minimum accessibility guidelines, and enable
-
- its client plug-ins to meet accessibility guidelines as well.
-
- <p><b><a name="Support revamped install and update story">Support
-
- revamped install and update story</a>.</b> PDE contains support for building
-
- the deployable form of a plug-in, or set of plug-ins. We will update PDE to
-
- support the revised install and update story.</p>
-
- <p><b><a name="Improve support for large scale multi-project plug-in development">Improve
-
- support for large scale multi-project plug-in development</a>.</b> We will improve support
-
- for large scale development efforts involving multiple plug-ins spread across
-
- several projects in the workspace.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Provide PDE API">Provide
- PDE API</a>.</b> We will add an extension point to allow plug-ins to
- contribute wizards from creating new extensions in the PDE Plug-in Manifest
- editor, and expose PDE API needed by clients that provide such wizards. <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Source builds">Source builds</a>.</b> In 1.0, the process used to
- create new Eclipse SDK drops from sources is only usable by the original
- development team. In 2.0, the magic will be removed and replaced by
- generally available scripts that anyone can use to build Eclipse SDK
- drops from sources.
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse PDE subproject.)
-
-</body>
-
-</html>
-
diff --git a/eclipse_project_plan_2_0_rev0326.html b/eclipse_project_plan_2_0_rev0326.html
deleted file mode 100644
index 8a09a0d..0000000
--- a/eclipse_project_plan_2_0_rev0326.html
+++ /dev/null
@@ -1,1353 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-
-<html>
-
-<head>
-
- <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-
- <meta name="Author" content="Eclipse Project PMC">
-
- <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-
- <meta name="ProgId" content="FrontPage.Editor.Document">
-
- <title>Eclipse Project 2.0 Plan</title>
-
- <link rel="stylesheet" href="../default_style.css" type="text/css">
-
-</head>
-
-<body>
-
-
-
-<h1>
-
-Eclipse Project<br>
-
-DRAFT 2.0 Plan</h1>
-
-Last revised Friday, March 22, 2002 [<u><font color="#008000">noting changes since
-previous draft plan Friday, December 21, 2001</font></u>]
-<p><i> Please send comments about this draft plan to the </i><a href="mailto:eclipse-dev@eclipse.org">eclipse-dev@eclipse.org</a>
-<i>developer mailing list.</i></p>
-
-<p>This document lays out the plan for the next major release of the Eclipse Project,
- designated release 2.0. The main emphasis of the Eclipse Project 2.0 release
- will be on improving quality (bug fixing) and performance, with a lesser emphasis
- on adding new features and APIs.
-<p>This plan serves at least two purposes. First, it serves as the blueprint guiding
- the efforts of the developers working on the Eclipse Project subprojects. The
- work items committed in this plan were selected over all others because they
- were judged to provide the most value to customers for this follow-on to the
- Eclipse Project 1.0 release. Second, this plan serves as an important input
- to the planning processes of the various customers of the Eclipse Platform.
- This plan tells them what to expect (or what not to expect) in the next release
- so that they can plan their projects accordingly.
-<p>Plans are rarely completely unchanging over the life cycle of a release, and
- this project is no exception. We will update this document as required to reflect
- any changes to the 2.0 release plan. While we certainly do not expect to backtrack
- on items already committed, we do anticipate adding further committed items
- to the list. This plan already includes a number of extra work items which we
- are presently unable to commit to for the 2.0 release due to time, but which
- are nonetheless worthy of being solved. Where possible, we will try to complete
- these items, and will revise this plan as soon as we know we can make a definite
- commitment. The individual Eclipse Project <a href="http://www.eclipse.org/eclipse/index.html" target="_top">subproject
- and component web pages</a> and <a href="http://www.eclipse.org/mail/index.html" target="_top">developer
- mailing list archives</a> contain further, in-depth information about how a
- component is changing. Particular problem reports being worked on for the 2.0
- release can be tracked through the <a href="http://dev.eclipse.org/bugs/">bug
- database</a>; the "Target Milestone" field reflects when a work item
- will become available in the main development stream.
-<p>[<font color="#008000"><u>This draft plan has changed significantly over the
- previous draft dated December 21, 2001. The Eclipse SDK user community has told
- us that they want to see additional improvements in certain areas, and that
- an early release that did not address their needs would be less interesting,
- and would only delay the availability of the follow-on release that did address
- their concerns. We therefore extended the development schedule to include a
- number of new committed items, many of which were previously known but on the
- uncommitted list. In addition, we deleted a few uncommitted items that we know
- will not be done in the Eclipse Project 2.0 release, and revised several items
- to more accurately describe what we will be doing. We added 3 more milestones
- (M4, M5, M6), and are now targeting May 2002 for the Eclipse Project 2.0 release,
- rather than April.</u></font>]
-<h2>Release deliverables</h2>
-
-<p>The release deliverables are:
-
-<ul>
-
- <li>Source code release for Eclipse Project, available as versions tagged "R2_0"
- in the Eclipse Project <a href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.</li>
-
- <li>Eclipse Project SDK (includes Platform, JDT, and PDE source zips)
-
- (downloadable).</li>
-
- <li>Eclipse Platform runtime binary distribution (downloadable).</li>
-
- <li>JDT runtime binary distribution (downloadable).</li>
-
- <li>Eclipse SDK Examples (downloadable).</li>
-
-</ul>
-
-<h2>Release milestones</h2>
-
-<p>The release milestones are:</p>
-
-<ul>
-
- <li>December 7, 2001 - milestone 0 - stable build reflecting progress</li>
-
- <li>December 21, 2001 - milestone 1 - stable build reflecting good progress</li>
-
- <li>January 25, 2002 - milestone 2 - stable build reflecting significant
-
- progress</li>
-
- <li>February 15, 2002 - milestone 3 - stable build reflecting significant
-
- progress [<u><font color="#008000">former initial development freeze</font></u>]</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] March 22, 2002 - milestone
- 4 - stable build reflecting significant progress</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] April 12, 2002 - milestone
- 5 - stable build reflecting significant progress</li>
-
- <li>[<u><font color="#008000">new milestone</font></u>] May 3, 2002 - milestone
- 6 - stable build - feature complete - initial development freeze</li>
-
-</ul>
-
-<p>
-
-The 2.0 release is targeted for May 2002 [<u><font color="#008000">formerly
-April</font></u>]. All release deliverables will be available for download
-
-as soon as the release has been tested and validated in the target operating
-
-configurations listed below.</p>
-
-<h2>
-
-Target Operating Environments</h2>
-
-
-
-<p>Most of the Eclipse SDK is "pure" Java and has no direct dependence on the
- underlying operating system. The chief dependence is therefore on the Java 2
- Platform itself. The 2.0 release of the Eclipse Project will be written against
- version 1.3 of the Java 2 Platform APIs, and targeted to run on either version
- 1.3 or 1.4 of the Java 2 Runtime Environment, Standard Edition.</p>
-
-<p>We plan to test and validate the Eclipse SDK 2.0 on the most up-to-date Java
- 2 Platform implementations available. These are:</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="19%"><b>Operating system</b></td>
-
- <td width="24%"><b>Processor architecture</b></td>
-
- <td width="73%"><b>Java 2 Platforms</b></td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Microsoft<br>
-
- Windows</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for
-
- Microsoft Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Windows, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Microsoft
- Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Linux</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Linux, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="2">Sun Solaris</td>
-
- <td width="24%" rowspan="2">SPARC</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Solaris
-
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Solaris
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="19%">HP HP-UX</td>
-
- <td width="24%">hp9000 PA-RISC</td>
-
- <td width="73%"><span class="header">HP-UX SDK for the Java 2 platform,
-
- version 1.3.1 for hp9000 PA-RISC</span></td>
-
- </tr>
-
- <tr>
-
- <td width="19%">IBM AIX</td>
-
- <td width="24%">PowerPC</td>
-
- <td width="73%">IBM Developer Kit for AIX, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
-</table>
-
-<p><span class="header">The following table describes the combinations of operating
- system and Java 2 Platform used when testing the Eclipse SDK configurations.
- The status column indicates the level of testing: Primary means a full tested
- configuration; </span>Secondary means a configuration which is only lightly
- tested; Untested means a configuration that has received no testing, but which
- should work. Note that the Linux GTK configuration is considered early access
- for the 2.0 release; it will be tested, but it is known in advance that it will
- not be of product quality in this release.</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="11%"><b>Window system</b></td>
-
- <td width="28%"><b>Java 2 Platform<br>
-
- (see above table)</b></td>
-
- <td width="42%"><b>Operating Environment</b></td>
-
- <td width="19%"><b>Testing Status</b></td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="5">Win32</td>
-
- <td width="28%" rowspan="5">Windows on Intel x86</td>
-
- <td width="42%">Windows 2000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows XP</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows ME</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows 98SE</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows NT</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="6">Motif</td>
-
- <td width="28%" rowspan="3">
-
- <p>Linux on Intel x86</p>
-
- <p> </td>
-
- <td width="42%">RedHat Linux 7.2 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">
-
-SuSE Linux 7.3 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and XFree86 version 4.1.0</td>
-
- <td width="19%">Untested</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">Solaris on SPARC </td>
-
- <td width="42%">Sun Solaris 8 SPARC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">HP-UX on hp9000 PA-RISC</td>
-
- <td width="42%">HP-UX 11i hp9000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">AIX on PowerPC</td>
-
- <td width="42%">IBM
-
-AIX 5.1 on PowerPC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="3">GTK</td>
-
- <td width="28%" rowspan="3">Linux on Intel x86</td>
-
- <td width="42%">RedHat Linux 7.2 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%"> SuSE Linux 7.3 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and GTK 2.0</td>
-
- <td width="19%"><i>Early access; untested</i></td>
-
- </tr>
-
-</table>
-
-<h4>
-
-Internationalization</h4>
-
-<p> The Eclipse Platform 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.</p>
-
-
-
-<p>Latin-1 locales will be supported by the Eclipse SDK on all of the above operating
- environments; DBCS and BIDI locales will be supported by the Eclipse SDK only
- on Windows operating environments. [<font color="#008000"><u>In the previous
- draft, internationalization was planned only for Windows operating environments.</u></font>]
-<p>The Eclipse SDK will support the GB 18030, the new Chinese code page standard,
- on Windows 2000 and XP only. Note that GB 18030 also requires locale and character
- encoding support from the Java 2 Runtime Environment; this support is standard
- in version 1.4, and also available in some 1.3 JREs.
-<p>We will perform tests in German and Japanese locales.
-
-<h4>
-
-BIDI support</h4>
-
-<p> The Eclipse SDK 2.0 is a development environment targeted at technical professionals
- - not an end user application. However the Eclipse SDK 2.0 tools will permit
- technical professionals who are working in English to build Hebrew/Arabic end
- user Java programs which are themselves not based on the Eclipse SDK. The BIDI
- support in the Eclipse SDK 2.0 allows a Java programmer to work with BIDI strings,
- code comments, etc but the Eclipse SDK itself is not designed to be localized
- for BIDI locales and its widget orientation can not be changed.</p>
-
-<p>IMPORTANT: The above BIDI support is available only on Windows platforms.</p>
-
-<h2>
-
-Compatibility with Previous Release</h2>
-
-The Eclipse SDK 2.0 will be upwards compatible with the Eclipse SDK 1.0 to the
-greatest extent possible. We anticipate a small number of areas where slavishly
-maintaining compatibility would not be in the best interests of the Platform or
-its clients. All such exceptions will be noted in the 2.0 release notes so that
-clients can assess the impact of these changes on their plug-ins and products.
-<p><b>Status of interim 1.0 APIs and plug-ins</b>: Some of the Eclipse SDK APIs
- and plug-ins in 1.0 were marked as provisional (debug, for instance). These
- APIs and plug-ins will either appear in stable, finished form in the 2.0 release,
- or be removed. As anticipated (and advertised), these API changes will likely
- break 1.0 client plug-ins that made use of that particular API in its early
- form. Even if code appears to work with 2.0, it would still need to be completely
- reviewed to ensure that it abides by the final API contracts.</p>
-
-<p><b>API Contract Compatibility:</b> The Eclipse SDK 2.0 will be upwards contract-compatible
- with the Eclipse SDK 1.0 unless noted. This means that programs in full compliance
- with contracts specified in the Eclipse SDK 1.0 APIs will automatically be in
- full compliance with the Eclipse SDK 2.0 APIs. (API is construed broadly to
- include such things as plug-in extension points.) Downward contract compatibility
- is not supported. There is no guarantee that compliance with the Eclipse SDK
- 2.0 APIs would ensure compliance with the Eclipse SDK 1.0 APIs.
-<p><b>Binary (plug-in) Compatibility:</b> The Eclipse SDK 2.0 will be upwards
- binary-compatible with the Eclipse SDK 1.0 unless noted. This means that plug-ins
- built for the Eclipse SDK 1.0 will continue to work correctly in the Eclipse
- SDK 2.0 without change. Downward plug-in compatibility is not supported. Plug-ins
- for the Eclipse SDK 2.0 are unlikely to be usable in the Eclipse SDK 1.0. Plug-ins
- with hard-coded references in their plug-in manifest file to 1.0 versions of
- prerequisite Eclipse Project plug-ins will not work in 2.0 as the plug-in version
- numbers will be incompatible.
-<p><b>Source Compatibility:</b> The Eclipse SDK 2.0 will be upwards source-compatible
- with the Eclipse SDK 1.0 unless noted. This means that source files written
- to use the Eclipse SDK 1.0 APIs can be successfully compiled and run against
- the Eclipse SDK 2.0 APIs. Since source incompatibilities are easy to deal with,
- maintaining source compatibility is considered much less important than maintaining
- contract and binary compatibility. Downward source compatibility is not supported.
- If source files use new Eclipse SDK APIs, they will not be usable with an earlier
- version of the Eclipse SDK.
-<p><b>Workspace Compatibility:</b> Eclipse SDK 2.0 will be upwards
-
-workspace-compatible with Eclipse SDK 1.0 unless noted. This means that
-
-workspaces and projects created with Eclipse SDK 1.0 can be successfully opened by Eclipse SDK
-
-2.0 and upgraded to a 2.0 workspace. Individual plug-ins developed for
-
-Eclipse SDK 1.0 should provide similar upwards compatibility for their workspace
-
-metadata; plug-in developers are responsible for ensuring that their plug-ins
-
-recognize 1.0 metadata and process it appropriately. Note: the interim
-
-Eclipse SDK 1.0 plug-ins (ones with provisional APIs) are unlikely to automatically
-
-upgrade their metadata to 2.0. User interface session state may be discarded
-when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created
-
-(or opened) by Eclipse SDK 2.0 will be unusable with an earlier version
-
-of Eclipse SDK.
-
-<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and certainly
- everything in a package with "internal" in its name, are considered
- implementation details which may vary between operating environment and are
- subject to change without notice. Client plug-ins that directly depend on anything
- other than what is specified in the Eclipse SDK API are inherently unsupportable
- and receive no guarantees about compatibility within a single release much less
- with an earlier release. Refer to <i><a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
- to Use the Eclipse API</a></i> for information about how to write compliant
- plug-ins.
-<h2> Eclipse Project Subprojects</h2>
-
-The Eclipse Project consists of 3 subprojects. Each subproject
-
-is covered in its own section:
-
-<blockquote><font size=+0><a href="#Eclipse Platform subproject">Eclipse Platform</a></font>
-
-<br><font size=+0><a href="#Java development tooling (JDT) subproject">JDT - Java development tooling</a></font>
-
-<br><font size=+0><a href="#Plug-in development environment (PDE) subproject">PDE - Plug-in development environment</a></font></blockquote>
-
-<p>For each subproject, the items listed reflect new features of the Eclipse Platform,
- or areas where existing features will be significantly reworked. Each item indicates
- the component affected by that work item (many items involve coordinated changes
- to several components).
-<p>Note that fixing bugs, improving test coverage, documentation, examples,
-
-etc. are considered routine ongoing maintenance activities and are not
-
-included in this plan unless they would also involve significant changes to the Platform.
-
-<h3>
-
-<a name="Eclipse Platform subproject">Eclipse Platform subproject</a></h3>
-
-The following items reflect new features of the Eclipse Platform, or areas
-
-where existing features will be significantly reworked. Each item indicates
-
-the component affected by that work item (some items involve coordinated
-
-changes to several components). Additional uncommitted items affecting these
-
-components are listed in the <a href="#Uncommitted Items">Uncommitted Items</a>
-
-section at the end.
-
-<h4>
-
-Platform Core component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform
-
-Core component</a> covers most of the Platform's non-UI infrastructure,
-
-including the basic plug-in mechanism, resources in the workspace. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve Platform startup times">Improve Platform
-
-startup times</a>.</b> Eclipse Platform startup times 1.0 reflect the speed of XML parsing for plug-in manifest files. As the sheer number of available
-
-plug-ins can be expected to increase by an order of magnitude in the near future,
-
-we need a more scalable solution to this problem. An improvement in startup
-
-time will come with computing and caching the plug-in registry on disk.
- <p>[<u><font color="#008000">Replacement item</font></u>] <b><a name="Improve Ant integration and the build story">Improve
- Ant integration and the build story</a>.</b> In 1.0, Ant is not as well integrated
- into the workbench as it could be. In 2.0, we plan to make it more convenient
- to run Ant scripts from the Workbench, including ones not originally written
- for use inside the platform. We also plan to make the platform's build story
- more transparent, and allow Ant steps to be included. These changes impact
- the UI component as well. [formerly called <a name="Improve Ant integration"><b>Provide
- first-class Ant integration</b></a><b>]</b>
- <p><a name="Improve serviceability"><b>Improve serviceability</b></a><b>.</b>
-
-Several factors make it difficult in 1.0 to debug an Eclipse Platform that
-
-is failing in the field: startup failures are poorly diagnosed; error messages in the log sometimes contain little
-
-or no useful information; the internal plug-in log file is busy while the
-
-Platform is running, and gets erased as soon as the Platform is restarted.
-
-We plan to improve the startup sequence, eliminate unhelpful error messages, take steps to help identify
-
-which plug-in is the apparent source of an internal error, and ensure that
-
-the information in the internal logs is more readily accessible. These changes will
-
-also impact the UI component.<p>[<font color="#008000"><u>Replacement
- for previously uncommitted item</u></font>] <b><a name="Allow VCM control over rename/move/delete">Allow VCM control over
- rename/move/delete</a>.</b> VCM providers sometimes need tighter control over how project resources are manipulated in the local file system. For instance, a project directory might be a specially mounted remote file system located on a VCM server, and require special server communication in order to delete, move, or change the name of a resource. Or the VCM provider may track version history across move/renames. (Other clients would like a similar opportunity to veto inappropriate name changes to their resources; this is a different concern.) We will add a headless callback so that the relevant VCM provider will be able to control moves, renames, and deletes. These changes will affect the VCM
- component as well.
-
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Support unmanaged resources in managed projects"><b>Support
-
-unmanaged resources in managed projects</b></a><b>.</b> Workspace projects often contain
-
-files derived by processing other files; it is usually the case that these
-
-derived files should not be under VCM, even though the rest of the files
-
-in the project are. Workspace projects may also contain extra files or
- directories in which the VCM provider stores metadata; however, these files
- are not of direct interest to either the user or to regular plug-ins. There needs to be some means of dealing with
- these;
-
-depending on the solution, this may require support from the UI as well as Core.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve support for product branding">Improve
- support for product branding</a>.</b> We will make it easier to furnish custom product
- information such as splash screens, product startup configuration, distinctive icons for
- product branding, product-specific preference settings, etc.</blockquote>
-
-
-
-<h4>
-
-Installation and Update component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html"> Installation and Update component</a> is responsible for installing and upgrading the Eclipse
-
-Platform in the field. Eclipse SDK 1.0 contains an early version
-
-of this component; it will be thoroughly reworked for 2.0. The following items
-
-are committed for 2.0:
-
-<blockquote>
-
- <p><b><a name="Redesign plug-in install and update story">Redesign
-
-plug-in installation and update story</a>.</b> The 1.0 concepts of <i>component</i>
-
- and <i>configuration</i> will be replaced with a new concept called a <i>feature</i>.
-
- Features define the packaging structure for a group of related plug-ins,
-
- plug-in fragments, and optionally non-plug-in files. This change impacts the Core
-
-component and the PDE subproject as well.</p>
-
- <p><b><a name="Improve installer flexiblilty">Improve installer </a><a name="Improve installer flexiblilty">flexibility</a>.</b>
-
- The standard Platform installer will be more flexible and support alternate
-
- packaging and site management schemes: structured site map for discovering
-
- available updates; improved granularity of downloads; accommodate native
-
- installers; feature-specific custom installers packaged with feature and
-
- executed during feature installation.</p>
-
-</blockquote>
-
-
-
-<h4>
-
-Platform UI component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html">Platform
-
-UI component</a> provides the generic workbench UI for the Eclipse Platform. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve accessibility - UI">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required to meet minimum
-
- accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The workbench and its standard views and wizards must meet minimum
-
- accessibility guidelines, including mouse-less operation. The Eclipse Platform
-
- needs to enable other client plug-ins to meet accessibility guidelines too.
-
- This change also impacts the SWT component.
-
- <p><b><a NAME="Improve editor management">Improve editor management</a>.</b>
-
-Users are finding it difficult to work with many editors open simultaneously
-
-in the Eclipse SDK 1.0 workbench, all seemingly stemming from the way editors
-
-are currently managed. The workbench's approach to editor management will
-
-be reviewed and revised to improve usability.
-
-<p><b><a name="Improve interaction between editors and views">Improve
-
-interaction between editors and views</a>.</b> There are some unfortunate interactions
-
-between editors and views in Eclipse SDK 1.0 that make it difficult for views
-
-to serve as "secondary windows" to an editor. Among other things, this
-
-leads to poor integration of standard views. The workbench's current approach
-
-to editors and views will be reviewed and revised to facilitate interaction
-
-and improve integration.
-
-<p><b><a name="Allow context menu contributions in Outline view">Allow
-
-context menu contributions in Outline view</a>.</b> In Eclipse SDK 1.0, clients
-
-have no control over the standard Outline view's popup context menu. This
-
-will be addressed so that clients will be able to make contributions to
-
-this menu.
-
-<p><b><a name="Improve usability re: losing context">Improve usability
-
-re: losing context</a>.</b> Some users have reported getting lost in the UI
-
-and having to close all open editors and perspectives to get their workbench
-
-back into a familiar state. The current approach will be reviewed and revised
-
-to improve usability.
-
-<p><b><a name="Improve the Task view">Improve the Task view</a>.</b> The
-
-standard Task view will be improved in the following areas: performance and
-
-usability for large numbers of items in the view; context-sensitive help; and
-
-making contributions to the view's context menu.<p><b><a name="Add support for working sets">Add support for working
-
- sets</a>.</b> In 1.0, all resources in the workspace are equally accessible.
-
- The workbench will let the user define working sets of resources, suitable for
-
- providing more restricted contexts for browsing, searching, and the like.
-
-<p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Improve usability of project natures"><b>Improve
-
-usability of project natures</b></a><b>.</b> In Eclipse SDK 1.0, project natures are secretly
-
-configured by the plug-ins that define them, leading to problems and blind
-
-spots when projects have other natures as well. We will enrich the underlying
-support for natures by adding declarative constraints between natures, and
-expose them to the user in the form of "capabilities" which the user
-may (re-)configure their project with. These
-
-changes also affect the Core component.
-
-<p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve consistency of saving workbench state"><b>Improve
-
-consistency of saving workbench state</b></a><b>.</b> In Eclipse SDK 1.0, there are a
-
-number of instances where user-configurable UI settings are not being persisted
-
-between sessions. The UI will provide better support for saving important
-
-UI state.
-
- <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Improve support for file encodings">Improve support for file encodings</a>.</b>
- Editors and other tools need to have the correct file encoding in order to
- read or write text files. In Eclipse SDK 1.0, everything uses the default file
- encoding for the current locale. We will improve this for Eclipse SDK 2.0.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Improve support for clipboard-based cut/copy/paste">Improve
- support for clipboard-based cut/copy/paste</a>.</b> There are several places in the
- workbench where cut/copy/paste are not enabled where
- they should be. The UI will allow clients to supply these actions so they work
- as expected.</blockquote>
-
-
-
-<h4>
-
-SWT component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html">SWT
-component</a> is the low-level widget toolkit used in the Eclipse Platform. The
-following items are committed for 2.0:
-<blockquote>
-
- <p><b><a name="Port to other window systems">Support additional window
-
- systems</a>.</b> Add support for new window system: GTK. Port Motif-based
-
- implementation to other operating systems: AIX, HP-UX, Solaris. Foster and
-
- encourage efforts to port to other window systems.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Support GB18030"><b>Support
- GB18030</b></a><b>.</b> GB 18030 is a new Chinese code page standard. Products
- shipping into the China market are required to support this new standard.
- The GB 18030 character encoding support is standard in Java 2 Runtime Environment
- version 1.4, and also available in some 1.3 JREs.
- <p><b><a name="Utilize native Unicode support">Utilize
-
- Windows native Unicode support</a>.</b> The SWT implementation will use
-
- native Unicode support on all Windows operating systems that support it (NT,
-
- 2000, XP).<p><b>Improve Motif appearance and performance.</b> In 1.0,
-
- support for the Motif window system lags behind that of Windows. We plan to improve the
-
- appearance and performance of SWT on Motif.
- <p><font FACE="Times New Roman" COLOR="#000000">[</font><u><font FACE="Times New Roman" COLOR="#008000">New
- item</font></u><font FACE="Times New Roman" COLOR="#000000">] <b>Remove
- internal call to XinitThreads</b>. In 1.0 on Motif, the internal call that SWT
- makes on XinitThreads prevents drag and drop, and printing from working. In
- 2.0, we will find a way to remove this impediment.</font></p>
-
-</blockquote>
-
-
-
-<h4>
-
-VCM component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> VCM component</a> provides version and configuration management for projects
-
-in the workspace and attendant team support. The following items are committed for 2.0:
-
-<blockquote><a name="Provide VCM API"><b>Provide an open VCM </b></a><b><a name="Provide VCM API">story</a>.</b> Eclipse SDK
-
-1.0 includes CVS repository support, but has no official VCM API that allows
-
-other version and configuration management systems to integrate into the
-
-Platform. We will provide a simple API, extension points, and usage guidelines
-
-so that VCM providers can adapt their repositories and integrate VCM product-specific
-
-UI elements into the Eclipse SDK UI.
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve CVS repository integration"><b>Improve
- CVS repository integration</b></a><b>.</b> In addition to converting the existing
- CVS repository adapter to the new VCM API, CVS support will be improved, including:
- support for CVS modules so that the platform can be connected to existing
- CVS repositories; support for CVS patch facility so that CVS users can capture
- changes to a project in a tangible form that can be submitted to others or
- archived (this also involves the compare infrastructure); correct classification
- of text and binary files.
-</blockquote>
-
-
-
-<ul><a name="Add mechanism for validating edits and saves"><b>Add mechanism
-
-for validating edits and saves</b></a><b>.</b> Some VCM providers require a "heads up" when the user starts
-
-to change the contents of a file open in an editor (e.g., to allow the file to
-
- be checked out and locked), or when the user is about to save the changed contents
-
-back to disk. We will add a callback so that the relevant VCM provider will be
-
- able to register for advance notification with an opportunity to veto. This
-
- change also affects the UI and Core components.<p> <b><a name="Add non-versioning WebDAV repository support">Add non-versioning
- WebDAV repository
- support</a>.</b>
-
- We plan to build a simple repository adapter for non-versioning WebDAV
- servers. This will allow users to share their files via any WebDAV compliant
- server. This also affects the Core component (target management API).</p>
-
-</ul>
-
-
-
-<h4>
-
-Help component</h4>
-
-
-
-<p>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html"> Help component</a> organizes help contributions and presents them to the
-
-user. The following items are committed for 2.0:</p>
-
-<blockquote><p><b><a name="Simplify contribution mechanism">Simplify
-
- contribution mechanism</a>.</b> Based on feedback on 1.0, we plan to rework
-
- and simplify the help contribution mechanism. Online documentation created for 1.0 will
-
- need to be converted for 2.0.<p>[<u><font color="#008000">Revised
- item</font></u>] <a name="Use a separate web browser to present help"><b>Use
-
-a separate web browser to present help</b></a><b>.</b> We will use an external
-
- web browser launched in a separate window to present all documentation and online help. This will allow help to be presented in a non-modal way.
- We will support one help browser for each target environment. Refer to the
- <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/eclipse_project_plan_2_0_supported_browsers.html">table</a>
- in the Help Component for additional information on supported browsers.
- <p><b><a name="Support live help">Support live help</a>.</b> We will support
- the ability to trigger developer-supplied actions as a result of navigating
- a link in the online documentation. The actions will execute within the Eclipse
- Platform environment.
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow remote help content">Enable
- help server</a>s.</b> It is often desirable to be able to make plug-in documentation
- accessible to users that do not have the Eclipse Platform installed. We will
- support configurations where online documentation can be hosted on a web server
- and viewed through a regular web browser. [<u><font color="#008000">The former
- "Info Center" item has been merged with this one.</font></u>]
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support standalone help">Support
- standalone help</a>.</b> Developers will be able to reuse the Eclipse Platform
- help function even in products that are not built using the Eclipse Platform
- itself.
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>]
- <a name="Add help search support"><b>Add help search support</b></a><b>.</b>
-
- We will provide the ability to search help documentation, based on <a href="http://jakarta.apache.org/lucene/docs/index.html">Lucene</a>.
- Stemmers will be used when available for the language; for example, the Porter
- stemming algorithm is used for English.
-
-</blockquote>
-
-
-
-<h4>
-
-Platform Debug component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html">Platform
-
-Debug component</a> provides generic Core and UI for launching, running, and debugging
-
-programs. The following items are committed for 2.0:
-
-<blockquote><a name="Stabilize Debug API"><b>Stabilize Debug API</b></a><b>.</b>
-
-In Eclipse SDK 1.0, all debug APIs were considered provisional and incomplete.
-
-The Debug APIs will appear in finished, stable form.</blockquote>
-
-
-
-<blockquote><a name="Add support for debugging procedural languages"><b>Add
-
-support for debugging procedural languages</b></a><b>.</b> The Debug component will be extended to
-
- enable debuggers to be written for procedural languages (e.g., C) which get compiled to machine code and run
-
-on standard hardware.
-
-<p><a name="Add launch configurations"><b>Add launch configurations</b></a><b>.</b>
-
-The Debug component will add a general mechanism and UI for the user to define launch
-
-configurations describing how something is to be launched (e.g., command
-
-line options).</blockquote>
-
-
-
-<h4>
-
-Scripting component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-scripting-home/main.html">Scripting
-component</a> provides general support for scripting (other than Ant). The following
-item is committed for 2.0:
-
-<blockquote>
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Remove Scripting component">Remove
- Scripting component</a>.</b>
-
-In Eclipse SDK 1.0, the scripting support was provisional and incomplete. It is now
- clear that we will not become real in the 2.0 timeframe. The Scripting
- component will be withdrawn from the Eclipse Platform (it may be
- re-introduced in a later release).</p>
-</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse Platform subproject)</h4>
-
-<p><i>N.B. The following is the list of important Eclipse Platform subproject
- work items which we are presently unable to commit to for the 2.0 release. Wherever
- possible, we will try to complete these items. Depending on how things work
- out, we should be able complete some of them. However, we cannot promise that
- we will complete any of them, and it would be unwise to gamble otherwise. Items
- not completed for 2.0 will carry over to the planning of the next release. We
- will revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-<ul>
- <p> <a name="Add support for non-local files"><b>Add support for non-local files</b></a><b>.</b>
- It is expensive to set up a workspace project containing a large number of
- files that normally reside on remote server or file system. Core has a basic
- mechanism that permits the workspace to contain placeholders for files and
- folders necessarily resident in the local file system. The Core mechanism
- will be augmented so that VCM can use it to hook it to retrieve files from
- a remote server or file system on demand. The UI component is also affected.
- <p> <a name="Improve undo/redo in workbench"><b>Improve undo/redo in workbench</b></a><b>.</b>
- In Eclipse SDK 1.0, undo and redo are poorly supported for workbench actions,
- and it is still far too easy for a user to lose work. We will consider providing
- an undo/redo service that will help decrease the risk of inadvertently losing
- work.
- <p><a name="Provide a standard Console view"><b>Provide a standard Console view</b></a><b>.</b>
- In Eclipse SDK 1.0, there is a proliferation of consoles furnished by clients
- (including JDT, PDE, Ant). The workbench will supply a standard Console view;
- clients will be encouraged to use it instead of providing their own. These
- changes will affect the UI component.
- <p>[<u><font color="#008000">Deleted item</font></u>] <a name="Improve support for cheat sheets"><b>Improve
- support for cheat sheets</b></a><b>.</b> In Eclipse SDK 1.0, the Welcome editor
- is an example of a cheat sheet. A cheat sheet is an instance of a simple kind
- of workflow support. We will continue to evolve the mechanisms behind cheat
- sheets, including adding standard API for creating actions. These changes
- will affect the UI component. [<font color="#008000"><u>This has turned out
- to require a major effort, so we are removing this uncommitted item from the
- 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide project interchange mechanism">Provide
- project interchange mechanism</a>.</b> We will provide a way to export the
- resources in one of more workspace projects to an archive file that it can
- be saved for posterity or imported to another workspace. This affects the
- Core and UI components. [<font color="#008000"><u>A consequence of the
- new VCM story is that we do not need to provide a special mechanism for project
- interchange. Therefore we are removing this uncommitted item from the 2.0
- plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide additional internationalization support">Provide
- additional internationalization support</a>.</b> We will enable the
- Eclipse Platform to provide internationalization support for additional locales
- on some Motif operating environments. This affects the SWT component. [<font color="#008000"><u>We
- have added support for additional locales (see the Internationalization section
- in this plan for more details). This uncommitted item is redundant,
- so we are removing it from the 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve local resource history">Improve
- local resource history</a>.</b> The workspace local resource history mechanism
- keeps recent copies of modified or deleted files in order to help save the
- user from losing data in common situations. In 1.0, many UI actions that the
- user would reasonably expect to grow the history are not doing so, and there
- is no obvious way to recover a saved state of a file once it has been deleted.
- We plan to make the history facility more reliable and helpful for 2.0.
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Add ftp repository support">Add
- ftp repository support</a>.</b> We plan to build a simple repository adapter
- for ftp servers. This also affects the Core component (target management API).</p>
-</ul>
-
-
-
-<p>(End of items for Eclipse Platform subproject.)
-
-
-
-<h3>
-
-<a name="Java development tooling (JDT) subproject">Java development tooling (JDT) subproject</a></h3>
-
-<a href="http://www.eclipse.org/jdt/index.html">
-
-Java development tooling</a> (JDT) implements a Java IDE based on the Eclipse
-
-Platform.
-
-The following committed items reflect new features of JDT, or areas where existing
-
-features will be significantly reworked.
-
-<blockquote><a name="Reduce memory footprint for Java builder"><b>Reduce
-
-memory footprint for Java builder</b></a><b>.</b> The internal data structures of
-
-the Java incremental compilation mechanism is using more memory than necessary
-
-or reasonable. By fundamentally changing the approach to how incremental
-
-builds are done we expect to substantially reduce the memory footprint
-
-without significantly increasing incremental compile times.
-
-<p><b><a name="Improve Java search">Improve Java search</a>.</b> Java reference
-
-searches in Eclipse SDK 1.0 are limited to named types in source files. This
-
-will be addresses so to make it possible to find references in JAR libraries, and to distinguish read and write accesses to fields.
-
- <p><a name="Improve code assist"><b>Improve code assist</b></a><b>.</b> A number
-
-of changes will improve usability of code assist: including method argument
-
-names and types as hints; suggesting variable names; honoring visibility
-
-constraints dictated by the context.
-
-<p><b><a name="Upgrade Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform">Upgrade
-
-Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform</a>.</b>
-
-A new assertion feature was added in 1.4, and there were a few clarifications
-
-in obscure corners of the Java language specification. The Eclipse Java compiler
-
-will be upgraded to support 1.4, but will continue to support 1.3 via an option
-
-setting.
-
-<p><b><a name="Improve build classpath">Improve build classpath</a>.</b>
-
-By adding a mechanism for explicitly exporting libraries on a project's
-
-build classpath to downstream projects, it becomes possible to have a library
-
-project (one with a JAR and no source folder) that can stand in for a project
-
-containing source code. This change enables large scale development where
-
-source code is contained in multiple, related Java projects, by providing
-
-possibilities other than having all the source code projects in the workspace
-
-at all times (expensive to build). Plug-in development is a direct beneficiary.
-
- <p><b><a name="Improve accessibility - JDT">Improve accessibility</a>.</b> Applications
-
- selling to the US Government market are required by law to meet minimum accessibility
-
- guidelines (<a href="http://www.section508.gov/" target="_top">Section 508</a>).
-
- The JDT UI must meet minimum accessibility guidelines, and enable its client
-
- plug-ins to meet accessibility guidelines as well.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve Java editor"><b>Improve Java editor</b></a>. Rework
-
-menu bar contributions and context menu to improve usability; add a template
-
- facility with variable substitution; add navigation to a method's super
-
- implementation; add bracket matching; add error clueing; add line/column
- numbers.
-
-<p><b><a name="Improve refactoring">Improve refactoring</a>.</b>
-
-Implement additional refactorings: extract variable, inline temporary, push-up
-
-field/method, change method signature. Support reference updates in strings and
-
-comments for move/rename refactorings.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Improve refactoring">Improve package
-
-browsing</a></b>: Provide a more package-centric view for browsing. In 1.0, the
-
-Packages view presents packages grouped by their containers. We will continue to
-support the existing container based presentation; in addition, we are exploring
-alternatives. We
-
-will also add
-
-support to show the structure of a compilation unit in the Packages
-
-view.
-
-<p><b><a name="Facilitate string externalization">Facilitate
-
-</a><a name="Facilitate string externalization">string
-
-externalization</a></b><b>.</b> Add a wizard that
-
-allows the user to
-
-externalizing string literals in Java source code into standard Java resource bundles.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow runtime parameters to the configured">Allow runtime
-parameters to the configured</a>.</b> Using the new launch configuration mechanism
-
-provided by the Platform Debug component will allow the working directory, runtime classpath,
-
-boot classpath, extension directories, and other VM-type specific launch
-
-parameters to be configured.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support hot code replace when debugging JDK 1.4 targets">Support
- hot code replace when debugging compliant Java 1.4 targets</a>.</b> JDPA for
- version 1.4 of the Java 2 Platform allow a class to be updated while under
- the control of the debugger. In 1.0, this kind of support was only available
- for IBM J9 targets. The Java debugger will be changed to support both.
- Provide smart drop to frame that only removes affected frames from the stack.
- <p><b><a name="Enable JSP debugging with JPDA">Enable JSP debugging
-
-with JPDA</a>.</b> The Java debugger will enable JSP debugging via a flexible source lookup algorithm and breakpoint setting mechanism.
-
-<p><a name="Add debugger support for step filtering"><b>Add debugger
-
-support for step filtering</b></a><b>.</b> The Java debugger will avoid stepping into
-
-any class mentioned on a user-specified exclusion list.
-
-<p><b><a name="Improve data inspectors">Improve data inspectors</a>.</b> We will
-
-improve support in the debugger for inspecting objects, including running an
-
-object's toString method to obtain a readable string that may be more
-
-meaningful to the user.
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Add API for Java abstract syntax tree"><b>Add
-
-API for Java abstract syntax tree</b></a><b>.</b> In Eclipse SDK 1.0, refactoring uses
-
-compiler internals for parsing and walking the abstract syntax trees (ASTs)
-
-for Java source code. We will add API for creating and manipulating ASTs
-
-that can serve as the basis for other clients like refactoring. </p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <b><a name="Add field watchpoints">Support field
-
- watchpoints</a>.</b> We will add debugger support for field watchpoints.</p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve Java editor"><b>Support editor key bindings</b></a>. Add support for user-configurable key
-
- bindings in the Java editor. This requires changes in the Platform UI
-
- component.<p>[<u><font color="#008000">New item</font></u>] <b><a name="Add support for JUnit">Add
- support for JUnit</a>.</b> We will include special tooling for the popular <a href="http://www.junit.org/">JUnit
- unit test framework</a> to facilitate authoring and running of JUnit test
- cases.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Add support for Javadoc generation">Add support for Javadoc
- generation</a>.</b> We will add an action for generating Javadoc for a Java
- project (note: requires a standard JDK).<p>[<u><font color="#008000">New
- item</font></u>] <b>Improve navigating to Javadoc.</b>
- We will add quick keyboard navigation from names in Java source code to the
- corresponding Javadoc, including the API Javadoc for names declared in
- libraries.</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse JDT subproject)</h4>
-
-<p><i>N.B. The following is the list of important JDT subproject work items
-
-which we are presently unable to commit to for the 2.0 release. Wherever
-
-possible, we will try to complete these items. Depending on how things work out,
-
-we should be able complete some of them. However, we cannot promise that we will
-
-complete any of them, and it would be unwise to gamble otherwise. Items not
-
-completed for 2.0 will carry over to the planning of the next release. We will
-
-revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-
-
-<blockquote>
- <p> <a name="Add conditional breakpoints"><b>Support conditional
-
- breakpoints</b></a><b>.</b> We will add debugger support
-
- for conditional breakpoints
-
-with simple conditions, including simply object identity tests of the form
-
- "this == id" sufficient for object breakpoints.</p>
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse JDT subproject.)
-
-
-
-<h3>
-
-<a name="Plug-in development environment (PDE) subproject">Plug-in development environment (PDE) subproject</a></h3>
-
-The <a href="http://www.eclipse.org/pde/index.html"> plug-in development environment</a>
-(PDE) consists of tools for developing plug-ins for the Eclipse Platform.
-For 2.0, the goal is to maintain the level of PDE support present in 1.0 while
-adding the necessary extensions that allow it to be the tool of choice for self-hosted
-Eclipse Project development. The following items are committed for 2.0:
-<blockquote> <b><a name="Improve accessibility - PDE">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required by law to meet
-
- minimum accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The PDE UI must meet minimum accessibility guidelines, and enable
-
- its client plug-ins to meet accessibility guidelines as well.
-
- <p><b><a name="Support revamped install and update story">Support
-
- revamped install and update story</a>.</b> PDE contains support for building
-
- the deployable form of a plug-in, or set of plug-ins. We will update PDE to
-
- support the revised install and update story.</p>
-
- <p><b><a name="Improve support for large scale multi-project plug-in development">Improve
-
- support for large scale multi-project plug-in development</a>.</b> We will improve support
-
- for large scale development efforts involving multiple plug-ins spread across
-
- several projects in the workspace.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Provide PDE API">Provide
- PDE API</a>.</b> We will add an extension point to allow plug-ins to
- contribute wizards from creating new extensions in the PDE Plug-in Manifest
- editor, and expose PDE API needed by clients that provide such wizards. <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Source builds">Source builds</a>.</b> In 1.0, the process used to
- create new Eclipse SDK drops from sources is only usable by the original
- development team. In 2.0, the magic will be removed and replaced by
- generally available scripts that anyone can use to build Eclipse SDK
- drops from sources.
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse PDE subproject.)
-
-</body>
-
-</html>
-
diff --git a/eclipse_project_plan_2_0_rev0517.html b/eclipse_project_plan_2_0_rev0517.html
deleted file mode 100644
index 5196567..0000000
--- a/eclipse_project_plan_2_0_rev0517.html
+++ /dev/null
@@ -1,1342 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-
-<html>
-
-<head>
-
- <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-
- <meta name="Author" content="Eclipse Project PMC">
-
- <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-
- <meta name="ProgId" content="FrontPage.Editor.Document">
-
- <title>Eclipse Project 2.0 Plan</title>
-
- <link rel="stylesheet" href="../default_style.css" type="text/css">
-
-</head>
-
-<body>
-
-
-
-<h1>
-
-Eclipse Project<br>
-
-DRAFT 2.0 Plan</h1>
-
-<p>Last revised Friday, May 17, 2002 Milestone dates are superceded by more detailed
- <a href="freeze_plan_2_0.html">2.0 Freeze/Test/Fix Plan</a>.<br>
- Last revised Friday, April 18, 2002 [<u><font color="#008000">noting changes
- since previous draft plan Friday, December 21, 2001</font></u>] </p>
-<p><i> Please send comments about this draft plan to the </i><a href="mailto:eclipse-dev@eclipse.org">eclipse-dev@eclipse.org</a>
-<i>developer mailing list.</i></p>
-
-<p>This document lays out the plan for the next major release of the Eclipse Project,
- designated release 2.0. The main emphasis of the Eclipse Project 2.0 release
- will be on improving quality (bug fixing) and performance, with a lesser emphasis
- on adding new features and APIs.
-<p>This plan serves at least two purposes. First, it serves as the blueprint guiding
- the efforts of the developers working on the Eclipse Project subprojects. The
- work items committed in this plan were selected over all others because they
- were judged to provide the most value to customers for this follow-on to the
- Eclipse Project 1.0 release. Second, this plan serves as an important input
- to the planning processes of the various customers of the Eclipse Platform.
- This plan tells them what to expect (or what not to expect) in the next release
- so that they can plan their projects accordingly.
-<p>Plans are rarely completely unchanging over the life cycle of a release, and
- this project is no exception. We will update this document as required to reflect
- any changes to the 2.0 release plan. While we certainly do not expect to backtrack
- on items already committed, we do anticipate adding further committed items
- to the list. This plan already includes a number of extra work items which we
- are presently unable to commit to for the 2.0 release due to time, but which
- are nonetheless worthy of being solved. Where possible, we will try to complete
- these items, and will revise this plan as soon as we know we can make a definite
- commitment. The individual Eclipse Project <a href="http://www.eclipse.org/eclipse/index.html" target="_top">subproject
- and component web pages</a> and <a href="http://www.eclipse.org/mail/index.html" target="_top">developer
- mailing list archives</a> contain further, in-depth information about how a
- component is changing. Particular problem reports being worked on for the 2.0
- release can be tracked through the <a href="http://dev.eclipse.org/bugs/">bug
- database</a>; the "Target Milestone" field reflects when a work item
- will become available in the main development stream.
-<p>[<font color="#008000"><u>This draft plan has changed significantly over the
- previous draft dated December 21, 2001. The Eclipse SDK user community has told
- us that they want to see additional improvements in certain areas, and that
- an early release that did not address their needs would be less interesting,
- and would only delay the availability of the follow-on release that did address
- their concerns. We therefore extended the development schedule to include a
- number of new committed items, many of which were previously known but on the
- uncommitted list. In addition, we deleted a few uncommitted items that we know
- will not be done in the Eclipse Project 2.0 release, and revised several items
- to more accurately describe what we will be doing. We added 3 more milestones
- (M4, M5, M6), and are now targeting May 2002 for the Eclipse Project 2.0 release,
- rather than April.</u></font>]
-<h2>Release deliverables</h2>
-
-<p>The release deliverables are:
-
-<ul>
-
- <li>Source code release for Eclipse Project, available as versions tagged "R2_0"
- in the Eclipse Project <a href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.</li>
-
- <li>Eclipse Project SDK (includes Platform, JDT, and PDE source zips)
-
- (downloadable).</li>
-
- <li>Eclipse Platform runtime binary distribution (downloadable).</li>
-
- <li>JDT runtime binary distribution (downloadable).</li>
-
- <li>Eclipse SDK Examples (downloadable).</li>
-
-</ul>
-
-<h2><a name="Milestones"></a>Release milestones</h2>
-
-<p><b>** See the 2.0 <a href="freeze_plan_2_0.html">Freeze/Test/Fix</a> Plan for
- detailed final release schedule.</b></p>
-<p>The release milestones are:</p>
-
-<ul>
- <li>December 7, 2001 - Milestone 0 - (2.0 M0) - stable build reflecting progress</li>
- <li>December 21, 2001 - Milestone 1 - (2.0 M1) - stable build reflecting good
- progress</li>
- <li>January 25, 2002 - Milestone 2 - (2.0 M2) - stable build reflecting significant
- progress</li>
- <li>February 15, 2002 - Milestone 3 - (2.0 M3) - stable build reflecting significant
- progress [<u><font color="#008000">former initial development freeze</font></u>]</li>
- <li>[<u><font color="#008000">new milestone</font></u>] March 22, 2002 - Milestone
- 4 -(2.0 M4) - stable build reflecting significant progress</li>
- <li>[<u><font color="#008000">new milestone</font></u>] April 16, 2002 - (2.0
- M5) milestone 5 - stable build reflecting significant progress</li>
- <li>[<u><font color="#008000">new milestone</font></u>] May 17, 2002 - Milestone
- 6 (2.0 M6) - stable build - feature complete - initial development freeze</li>
-</ul>
-
-<p> The 2.0 release is targeted for June 2002 [<u><font color="#008000">formerly
- April</font></u>]. All release deliverables will be available for download as
- soon as the release has been tested and validated in the target operating configurations
- listed below.</p>
-
-<h2>Target Operating Environments</h2>
-
-
-
-<p>Most of the Eclipse SDK is "pure" Java and has no direct dependence on the
- underlying operating system. The chief dependence is therefore on the Java 2
- Platform itself. The 2.0 release of the Eclipse Project will be written against
- version 1.3 of the Java 2 Platform APIs, and targeted to run on either version
- 1.3 or 1.4 of the Java 2 Runtime Environment, Standard Edition.</p>
-
-<p>We plan to test and validate the Eclipse SDK 2.0 on the most up-to-date Java
- 2 Platform implementations available. These are:</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="19%"><b>Operating system</b></td>
-
- <td width="24%"><b>Processor architecture</b></td>
-
- <td width="73%"><b>Java 2 Platforms</b></td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Microsoft<br>
-
- Windows</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for
-
- Microsoft Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Windows, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Microsoft
- Windows</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="3">Linux</td>
-
- <td width="24%" rowspan="3">Intel x86</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">IBM Developer Kit for Linux, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Linux x86</td>
-
- </tr>
-
- <tr>
-
- <td width="19%" rowspan="2">Sun Solaris</td>
-
- <td width="24%" rowspan="2">SPARC</td>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Solaris
-
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Solaris
- SPARC</td>
-
- </tr>
-
- <tr>
-
- <td width="19%">HP HP-UX</td>
-
- <td width="24%">hp9000 PA-RISC</td>
-
- <td width="73%"><span class="header">HP-UX SDK for the Java 2 platform,
-
- version 1.3.1 for hp9000 PA-RISC</span></td>
-
- </tr>
-
- <tr>
-
- <td width="19%">IBM AIX</td>
-
- <td width="24%">PowerPC</td>
-
- <td width="73%">IBM Developer Kit for AIX, Java 2 Technology Edition, version 1.3.0</td>
-
- </tr>
-
-</table>
-
-<p><span class="header">The following table describes the combinations of operating
- system and Java 2 Platform used when testing the Eclipse SDK configurations.
- The status column indicates the level of testing: Primary means a full tested
- configuration; </span>Secondary means a configuration which is only lightly
- tested; Untested means a configuration that has received no testing, but which
- should work. Note that the Linux GTK configuration is considered early access
- for the 2.0 release; it will be tested, but it is known in advance that it will
- not be of product quality in this release.</p>
-
-<table border="1" width="91%">
-
- <tr>
-
- <td width="11%"><b>Window system</b></td>
-
- <td width="28%"><b>Java 2 Platform<br>
-
- (see above table)</b></td>
-
- <td width="42%"><b>Operating Environment</b></td>
-
- <td width="19%"><b>Testing Status</b></td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="5">Win32</td>
-
- <td width="28%" rowspan="5">Windows on Intel x86</td>
-
- <td width="42%">Windows 2000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows XP</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows ME</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows 98SE</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Windows NT</td>
-
- <td width="19%">Secondary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="6">Motif</td>
-
- <td width="28%" rowspan="3">
-
- <p>Linux on Intel x86</p>
-
- <p> </td>
-
- <td width="42%">RedHat Linux 7.2 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">
-
-SuSE Linux 7.3 x86</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and XFree86 version 4.1.0</td>
-
- <td width="19%">Untested</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">Solaris on SPARC </td>
-
- <td width="42%">Sun Solaris 8 SPARC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">HP-UX on hp9000 PA-RISC</td>
-
- <td width="42%">HP-UX 11i hp9000</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="28%">AIX on PowerPC</td>
-
- <td width="42%">IBM
-
-AIX 5.1 on PowerPC</td>
-
- <td width="19%">Primary</td>
-
- </tr>
-
- <tr>
-
- <td width="11%" rowspan="3">GTK</td>
-
- <td width="28%" rowspan="3">Linux on Intel x86</td>
-
- <td width="42%">RedHat Linux 7.2 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%"> SuSE Linux 7.3 x86 GTK 2.0</td>
-
- <td width="19%"><i>Early access</i></td>
-
- </tr>
-
- <tr>
-
- <td width="42%">Other Linux; kernel version 2.4.7, and GTK 2.0</td>
-
- <td width="19%"><i>Early access; untested</i></td>
-
- </tr>
-
-</table>
-
-<h4>
-
-Internationalization</h4>
-
-<p> The Eclipse Platform 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.</p>
-
-
-
-<p>Latin-1 locales will be supported by the Eclipse SDK on all of the above operating
- environments; DBCS and BIDI locales will be supported by the Eclipse SDK only
- on Windows operating environments. [<font color="#008000"><u>In the previous
- draft, internationalization was planned only for Windows operating environments.</u></font>]
-<p>The Eclipse SDK will support the GB 18030, the new Chinese code page standard,
- on Windows 2000 and XP only. Note that GB 18030 also requires locale and character
- encoding support from the Java 2 Runtime Environment; this support is standard
- in version 1.4, and also available in some 1.3 JREs.
-<p>We will perform tests in German and Japanese locales.
-
-<h4>
-
-BIDI support</h4>
-
-<p> The Eclipse SDK 2.0 is a development environment targeted at technical professionals
- - not an end user application. However the Eclipse SDK 2.0 tools will permit
- technical professionals who are working in English to build Hebrew/Arabic end
- user Java programs which are themselves not based on the Eclipse SDK. The BIDI
- support in the Eclipse SDK 2.0 allows a Java programmer to work with BIDI strings,
- code comments, etc but the Eclipse SDK itself is not designed to be localized
- for BIDI locales and its widget orientation can not be changed.</p>
-
-<p>IMPORTANT: The above BIDI support is available only on Windows platforms.</p>
-
-<h2>
-
-Compatibility with Previous Release</h2>
-
-The Eclipse SDK 2.0 will be upwards compatible with the Eclipse SDK 1.0 to the
-greatest extent possible. We anticipate a small number of areas where slavishly
-maintaining compatibility would not be in the best interests of the Platform or
-its clients. All such exceptions will be noted in the 2.0 release notes so that
-clients can assess the impact of these changes on their plug-ins and products.
-<p><b>Status of interim 1.0 APIs and plug-ins</b>: Some of the Eclipse SDK APIs
- and plug-ins in 1.0 were marked as provisional (debug, for instance). These
- APIs and plug-ins will either appear in stable, finished form in the 2.0 release,
- or be removed. As anticipated (and advertised), these API changes will likely
- break 1.0 client plug-ins that made use of that particular API in its early
- form. Even if code appears to work with 2.0, it would still need to be completely
- reviewed to ensure that it abides by the final API contracts.</p>
-
-<p><b>API Contract Compatibility:</b> The Eclipse SDK 2.0 will be upwards contract-compatible
- with the Eclipse SDK 1.0 unless noted. This means that programs in full compliance
- with contracts specified in the Eclipse SDK 1.0 APIs will automatically be in
- full compliance with the Eclipse SDK 2.0 APIs. (API is construed broadly to
- include such things as plug-in extension points.) Downward contract compatibility
- is not supported. There is no guarantee that compliance with the Eclipse SDK
- 2.0 APIs would ensure compliance with the Eclipse SDK 1.0 APIs.
-<p><b>Binary (plug-in) Compatibility:</b> The Eclipse SDK 2.0 will be upwards
- binary-compatible with the Eclipse SDK 1.0 unless noted. This means that plug-ins
- built for the Eclipse SDK 1.0 will continue to work correctly in the Eclipse
- SDK 2.0 without change. Downward plug-in compatibility is not supported. Plug-ins
- for the Eclipse SDK 2.0 are unlikely to be usable in the Eclipse SDK 1.0. Plug-ins
- with hard-coded references in their plug-in manifest file to 1.0 versions of
- prerequisite Eclipse Project plug-ins will not work in 2.0 as the plug-in version
- numbers will be incompatible.
-<p><b>Source Compatibility:</b> The Eclipse SDK 2.0 will be upwards source-compatible
- with the Eclipse SDK 1.0 unless noted. This means that source files written
- to use the Eclipse SDK 1.0 APIs can be successfully compiled and run against
- the Eclipse SDK 2.0 APIs. Since source incompatibilities are easy to deal with,
- maintaining source compatibility is considered much less important than maintaining
- contract and binary compatibility. Downward source compatibility is not supported.
- If source files use new Eclipse SDK APIs, they will not be usable with an earlier
- version of the Eclipse SDK.
-<p><b>Workspace Compatibility:</b> Eclipse SDK 2.0 will be upwards
-
-workspace-compatible with Eclipse SDK 1.0 unless noted. This means that
-
-workspaces and projects created with Eclipse SDK 1.0 can be successfully opened by Eclipse SDK
-
-2.0 and upgraded to a 2.0 workspace. Individual plug-ins developed for
-
-Eclipse SDK 1.0 should provide similar upwards compatibility for their workspace
-
-metadata; plug-in developers are responsible for ensuring that their plug-ins
-
-recognize 1.0 metadata and process it appropriately. Note: the interim
-
-Eclipse SDK 1.0 plug-ins (ones with provisional APIs) are unlikely to automatically
-
-upgrade their metadata to 2.0. User interface session state may be discarded
-when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created
-
-(or opened) by Eclipse SDK 2.0 will be unusable with an earlier version
-
-of Eclipse SDK.
-
-<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and certainly
- everything in a package with "internal" in its name, are considered
- implementation details which may vary between operating environment and are
- subject to change without notice. Client plug-ins that directly depend on anything
- other than what is specified in the Eclipse SDK API are inherently unsupportable
- and receive no guarantees about compatibility within a single release much less
- with an earlier release. Refer to <i><a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
- to Use the Eclipse API</a></i> for information about how to write compliant
- plug-ins.
-<h2> Eclipse Project Subprojects</h2>
-
-The Eclipse Project consists of 3 subprojects. Each subproject
-
-is covered in its own section:
-
-<blockquote><font size=+0><a href="#Eclipse Platform subproject">Eclipse Platform</a></font>
-
-<br><font size=+0><a href="#Java development tooling (JDT) subproject">JDT - Java development tooling</a></font>
-
-<br><font size=+0><a href="#Plug-in development environment (PDE) subproject">PDE - Plug-in development environment</a></font></blockquote>
-
-<p>For each subproject, the items listed reflect new features of the Eclipse Platform,
- or areas where existing features will be significantly reworked. Each item indicates
- the component affected by that work item (many items involve coordinated changes
- to several components).
-<p>Note that fixing bugs, improving test coverage, documentation, examples,
-
-etc. are considered routine ongoing maintenance activities and are not
-
-included in this plan unless they would also involve significant changes to the Platform.
-
-<h3>
-
-<a name="Eclipse Platform subproject">Eclipse Platform subproject</a></h3>
-
-The following items reflect new features of the Eclipse Platform, or areas
-
-where existing features will be significantly reworked. Each item indicates
-
-the component affected by that work item (some items involve coordinated
-
-changes to several components). Additional uncommitted items affecting these
-
-components are listed in the <a href="#Uncommitted Items">Uncommitted Items</a>
-
-section at the end.
-
-<h4>
-
-Platform Core component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform
-
-Core component</a> covers most of the Platform's non-UI infrastructure,
-
-including the basic plug-in mechanism, resources in the workspace. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve Platform startup times">Improve Platform
-
-startup times</a>.</b> Eclipse Platform startup times 1.0 reflect the speed of XML parsing for plug-in manifest files. As the sheer number of available
-
-plug-ins can be expected to increase by an order of magnitude in the near future,
-
-we need a more scalable solution to this problem. An improvement in startup
-
-time will come with computing and caching the plug-in registry on disk.
- <p>[<u><font color="#008000">Replacement item</font></u>] <b><a name="Improve Ant integration and the build story">Improve
- Ant integration and the build story</a>.</b> In 1.0, Ant is not as well integrated
- into the workbench as it could be. In 2.0, we plan to make it more convenient
- to run Ant scripts from the Workbench, including ones not originally written
- for use inside the platform. We also plan to make the platform's build story
- more transparent, and allow Ant steps to be included. These changes impact
- the UI component as well. [formerly called <a name="Improve Ant integration"><b>Provide
- first-class Ant integration</b></a><b>]</b>
- <p><a name="Improve serviceability"><b>Improve serviceability</b></a><b>.</b>
-
-Several factors make it difficult in 1.0 to debug an Eclipse Platform that
-
-is failing in the field: startup failures are poorly diagnosed; error messages in the log sometimes contain little
-
-or no useful information; the internal plug-in log file is busy while the
-
-Platform is running, and gets erased as soon as the Platform is restarted.
-
-We plan to improve the startup sequence, eliminate unhelpful error messages, take steps to help identify
-
-which plug-in is the apparent source of an internal error, and ensure that
-
-the information in the internal logs is more readily accessible. These changes will
-
-also impact the UI component.<p>[<font color="#008000"><u>Replacement
- for previously uncommitted item</u></font>] <b><a name="Allow VCM control over rename/move/delete">Allow VCM control over
- rename/move/delete</a>.</b> VCM providers sometimes need tighter control over how project resources are manipulated in the local file system. For instance, a project directory might be a specially mounted remote file system located on a VCM server, and require special server communication in order to delete, move, or change the name of a resource. Or the VCM provider may track version history across move/renames. (Other clients would like a similar opportunity to veto inappropriate name changes to their resources; this is a different concern.) We will add a headless callback so that the relevant VCM provider will be able to control moves, renames, and deletes. These changes will affect the VCM
- component as well.
-
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Support unmanaged resources in managed projects"><b>Support
-
-unmanaged resources in managed projects</b></a><b>.</b> Workspace projects often contain
-
-files derived by processing other files; it is usually the case that these
-
-derived files should not be under VCM, even though the rest of the files
-
-in the project are. Workspace projects may also contain extra files or
- directories in which the VCM provider stores metadata; however, these files
- are not of direct interest to either the user or to regular plug-ins. There needs to be some means of dealing with
- these;
-
-depending on the solution, this may require support from the UI as well as Core.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve support for product branding">Improve
- support for product branding</a>.</b> We will make it easier to furnish custom product
- information such as splash screens, product startup configuration, distinctive icons for
- product branding, product-specific preference settings, etc.</blockquote>
-
-
-
-<h4>
-
-Installation and Update component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html"> Installation and Update component</a> is responsible for installing and upgrading the Eclipse
-
-Platform in the field. Eclipse SDK 1.0 contains an early version
-
-of this component; it will be thoroughly reworked for 2.0. The following items
-
-are committed for 2.0:
-
-<blockquote>
-
- <p><b><a name="Redesign plug-in install and update story">Redesign
-
-plug-in installation and update story</a>.</b> The 1.0 concepts of <i>component</i>
-
- and <i>configuration</i> will be replaced with a new concept called a <i>feature</i>.
-
- Features define the packaging structure for a group of related plug-ins,
-
- plug-in fragments, and optionally non-plug-in files. This change impacts the Core
-
-component and the PDE subproject as well.</p>
-
- <p><b><a name="Improve installer flexiblilty">Improve installer </a><a name="Improve installer flexiblilty">flexibility</a>.</b>
-
- The standard Platform installer will be more flexible and support alternate
-
- packaging and site management schemes: structured site map for discovering
-
- available updates; improved granularity of downloads; accommodate native
-
- installers; feature-specific custom installers packaged with feature and
-
- executed during feature installation.</p>
-
-</blockquote>
-
-
-
-<h4>
-
-Platform UI component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html">Platform
-
-UI component</a> provides the generic workbench UI for the Eclipse Platform. The following
-
-items are committed for 2.0:
-
-<blockquote><b><a name="Improve accessibility - UI">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required to meet minimum
-
- accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The workbench and its standard views and wizards must meet minimum
-
- accessibility guidelines, including mouse-less operation. The Eclipse Platform
-
- needs to enable other client plug-ins to meet accessibility guidelines too.
-
- This change also impacts the SWT component.
-
- <p><b><a NAME="Improve editor management">Improve editor management</a>.</b>
-
-Users are finding it difficult to work with many editors open simultaneously
-
-in the Eclipse SDK 1.0 workbench, all seemingly stemming from the way editors
-
-are currently managed. The workbench's approach to editor management will
-
-be reviewed and revised to improve usability.
-
-<p><b><a name="Improve interaction between editors and views">Improve
-
-interaction between editors and views</a>.</b> There are some unfortunate interactions
-
-between editors and views in Eclipse SDK 1.0 that make it difficult for views
-
-to serve as "secondary windows" to an editor. Among other things, this
-
-leads to poor integration of standard views. The workbench's current approach
-
-to editors and views will be reviewed and revised to facilitate interaction
-
-and improve integration.
-
-<p><b><a name="Allow context menu contributions in Outline view">Allow
-
-context menu contributions in Outline view</a>.</b> In Eclipse SDK 1.0, clients
-
-have no control over the standard Outline view's popup context menu. This
-
-will be addressed so that clients will be able to make contributions to
-
-this menu.
-
-<p><b><a name="Improve usability re: losing context">Improve usability
-
-re: losing context</a>.</b> Some users have reported getting lost in the UI
-
-and having to close all open editors and perspectives to get their workbench
-
-back into a familiar state. The current approach will be reviewed and revised
-
-to improve usability.
-
-<p><b><a name="Improve the Task view">Improve the Task view</a>.</b> The
-
-standard Task view will be improved in the following areas: performance and
-
-usability for large numbers of items in the view; context-sensitive help; and
-
-making contributions to the view's context menu.<p><b><a name="Add support for working sets">Add support for working
-
- sets</a>.</b> In 1.0, all resources in the workspace are equally accessible.
-
- The workbench will let the user define working sets of resources, suitable for
-
- providing more restricted contexts for browsing, searching, and the like.
-
-<p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>] <a name="Improve usability of project natures"><b>Improve
-
-usability of project natures</b></a><b>.</b> In Eclipse SDK 1.0, project natures are secretly
-
-configured by the plug-ins that define them, leading to problems and blind
-
-spots when projects have other natures as well. We will enrich the underlying
-support for natures by adding declarative constraints between natures, and
-expose them to the user in the form of "capabilities" which the user
-may (re-)configure their project with. These
-
-changes also affect the Core component.
-
-<p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve consistency of saving workbench state"><b>Improve
-
-consistency of saving workbench state</b></a><b>.</b> In Eclipse SDK 1.0, there are a
-
-number of instances where user-configurable UI settings are not being persisted
-
-between sessions. The UI will provide better support for saving important
-
-UI state.
-
- <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Improve support for file encodings">Improve support for file encodings</a>.</b>
- Editors and other tools need to have the correct file encoding in order to
- read or write text files. In Eclipse SDK 1.0, everything uses the default file
- encoding for the current locale. We will improve this for Eclipse SDK 2.0.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Improve support for clipboard-based cut/copy/paste">Improve
- support for clipboard-based cut/copy/paste</a>.</b> There are several places in the
- workbench where cut/copy/paste are not enabled where
- they should be. The UI will allow clients to supply these actions so they work
- as expected.</blockquote>
-
-
-
-<h4>
-
-SWT component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html">SWT
-component</a> is the low-level widget toolkit used in the Eclipse Platform. The
-following items are committed for 2.0:
-<blockquote>
-
- <p><b><a name="Port to other window systems">Support additional window
-
- systems</a>.</b> Add support for new window system: GTK. Port Motif-based
-
- implementation to other operating systems: AIX, HP-UX, Solaris. Foster and
-
- encourage efforts to port to other window systems.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Support GB18030"><b>Support
- GB18030</b></a><b>.</b> GB 18030 is a new Chinese code page standard. Products
- shipping into the China market are required to support this new standard.
- The GB 18030 character encoding support is standard in Java 2 Runtime Environment
- version 1.4, and also available in some 1.3 JREs.
- <p><b><a name="Utilize native Unicode support">Utilize
-
- Windows native Unicode support</a>.</b> The SWT implementation will use
-
- native Unicode support on all Windows operating systems that support it (NT,
-
- 2000, XP).<p><b>Improve Motif appearance and performance.</b> In 1.0,
-
- support for the Motif window system lags behind that of Windows. We plan to improve the
-
- appearance and performance of SWT on Motif.
- <p><font FACE="Times New Roman" COLOR="#000000">[</font><u><font FACE="Times New Roman" COLOR="#008000">New
- item</font></u><font FACE="Times New Roman" COLOR="#000000">] <b>Remove
- internal call to XinitThreads</b>. In 1.0 on Motif, the internal call that SWT
- makes on XinitThreads prevents drag and drop, and printing from working. In
- 2.0, we will find a way to remove this impediment.</font></p>
-
-</blockquote>
-
-
-
-<h4>
-
-VCM component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> VCM component</a> provides version and configuration management for projects
-
-in the workspace and attendant team support. The following items are committed for 2.0:
-
-<blockquote><a name="Provide VCM API"><b>Provide an open VCM </b></a><b><a name="Provide VCM API">story</a>.</b> Eclipse SDK
-
-1.0 includes CVS repository support, but has no official VCM API that allows
-
-other version and configuration management systems to integrate into the
-
-Platform. We will provide a simple API, extension points, and usage guidelines
-
-so that VCM providers can adapt their repositories and integrate VCM product-specific
-
-UI elements into the Eclipse SDK UI.
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve CVS repository integration"><b>Improve
- CVS repository integration</b></a><b>.</b> In addition to converting the existing
- CVS repository adapter to the new VCM API, CVS support will be improved, including:
- support for CVS modules so that the platform can be connected to existing
- CVS repositories; support for CVS patch facility so that CVS users can capture
- changes to a project in a tangible form that can be submitted to others or
- archived (this also involves the compare infrastructure); correct classification
- of text and binary files.
-</blockquote>
-
-
-
-<ul><a name="Add mechanism for validating edits and saves"><b>Add mechanism
-
-for validating edits and saves</b></a><b>.</b> Some VCM providers require a "heads up" when the user starts
-
-to change the contents of a file open in an editor (e.g., to allow the file to
-
- be checked out and locked), or when the user is about to save the changed contents
-
-back to disk. We will add a callback so that the relevant VCM provider will be
-
- able to register for advance notification with an opportunity to veto. This
-
- change also affects the UI and Core components.<p> <b><a name="Add non-versioning WebDAV repository support">Add non-versioning
- WebDAV repository
- support</a>.</b>
-
- We plan to build a simple repository adapter for non-versioning WebDAV
- servers. This will allow users to share their files via any WebDAV compliant
- server. This also affects the Core component (target management API).</p>
-
-</ul>
-
-
-
-<h4>
-
-Help component</h4>
-
-
-
-<p>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html"> Help component</a> organizes help contributions and presents them to the
-
-user. The following items are committed for 2.0:</p>
-
-<blockquote><p><b><a name="Simplify contribution mechanism">Simplify
-
- contribution mechanism</a>.</b> Based on feedback on 1.0, we plan to rework
-
- and simplify the help contribution mechanism. Online documentation created for 1.0 will
-
- need to be converted for 2.0.<p>[<u><font color="#008000">Revised
- item</font></u>] <a name="Use a separate web browser to present help"><b>Use
-
-a separate web browser to present help</b></a><b>.</b> We will use an external
-
- web browser launched in a separate window to present all documentation and online help. This will allow help to be presented in a non-modal way.
- We will support one help browser for each target environment. Refer to the
- <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/eclipse_project_plan_2_0_supported_browsers.html">table</a>
- in the Help Component for additional information on supported browsers.
- <p><b><a name="Support live help">Support live help</a>.</b> We will support
- the ability to trigger developer-supplied actions as a result of navigating
- a link in the online documentation. The actions will execute within the Eclipse
- Platform environment.
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow remote help content">Enable
- help server</a>s.</b> It is often desirable to be able to make plug-in documentation
- accessible to users that do not have the Eclipse Platform installed. We will
- support configurations where online documentation can be hosted on a web server
- and viewed through a regular web browser. [<u><font color="#008000">The former
- "Info Center" item has been merged with this one.</font></u>]
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support standalone help">Support
- standalone help</a>.</b> Developers will be able to reuse the Eclipse Platform
- help function even in products that are not built using the Eclipse Platform
- itself.
- <p>[<u><font color="#008000">Previously uncommitted item (revised)</font></u>]
- <a name="Add help search support"><b>Add help search support</b></a><b>.</b>
-
- We will provide the ability to search help documentation, based on <a href="http://jakarta.apache.org/lucene/docs/index.html">Lucene</a>.
- Stemmers will be used when available for the language; for example, the Porter
- stemming algorithm is used for English.
-
-</blockquote>
-
-
-
-<h4>
-
-Platform Debug component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html">Platform
-
-Debug component</a> provides generic Core and UI for launching, running, and debugging
-
-programs. The following items are committed for 2.0:
-
-<blockquote><a name="Stabilize Debug API"><b>Stabilize Debug API</b></a><b>.</b>
-
-In Eclipse SDK 1.0, all debug APIs were considered provisional and incomplete.
-
-The Debug APIs will appear in finished, stable form.</blockquote>
-
-
-
-<blockquote><a name="Add support for debugging procedural languages"><b>Add
-
-support for debugging procedural languages</b></a><b>.</b> The Debug component will be extended to
-
- enable debuggers to be written for procedural languages (e.g., C) which get compiled to machine code and run
-
-on standard hardware.
-
-<p><a name="Add launch configurations"><b>Add launch configurations</b></a><b>.</b>
-
-The Debug component will add a general mechanism and UI for the user to define launch
-
-configurations describing how something is to be launched (e.g., command
-
-line options).</blockquote>
-
-
-
-<h4>
-
-Scripting component</h4>
-
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-scripting-home/main.html">Scripting
-component</a> provides general support for scripting (other than Ant). The following
-item is committed for 2.0:
-
-<blockquote>
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Remove Scripting component">Remove
- Scripting component</a>.</b>
-
-In Eclipse SDK 1.0, the scripting support was provisional and incomplete. It is now
- clear that we will not become real in the 2.0 timeframe. The Scripting
- component will be withdrawn from the Eclipse Platform (it may be
- re-introduced in a later release).</p>
-</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse Platform subproject)</h4>
-
-<p><i>N.B. The following is the list of important Eclipse Platform subproject
- work items which we are presently unable to commit to for the 2.0 release. Wherever
- possible, we will try to complete these items. Depending on how things work
- out, we should be able complete some of them. However, we cannot promise that
- we will complete any of them, and it would be unwise to gamble otherwise. Items
- not completed for 2.0 will carry over to the planning of the next release. We
- will revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-<ul>
- <p> <a name="Add support for non-local files"><b>Add support for non-local files</b></a><b>.</b>
- It is expensive to set up a workspace project containing a large number of
- files that normally reside on remote server or file system. Core has a basic
- mechanism that permits the workspace to contain placeholders for files and
- folders necessarily resident in the local file system. The Core mechanism
- will be augmented so that VCM can use it to hook it to retrieve files from
- a remote server or file system on demand. The UI component is also affected.
- <p> <a name="Improve undo/redo in workbench"><b>Improve undo/redo in workbench</b></a><b>.</b>
- In Eclipse SDK 1.0, undo and redo are poorly supported for workbench actions,
- and it is still far too easy for a user to lose work. We will consider providing
- an undo/redo service that will help decrease the risk of inadvertently losing
- work.
- <p><a name="Provide a standard Console view"><b>Provide a standard Console view</b></a><b>.</b>
- In Eclipse SDK 1.0, there is a proliferation of consoles furnished by clients
- (including JDT, PDE, Ant). The workbench will supply a standard Console view;
- clients will be encouraged to use it instead of providing their own. These
- changes will affect the UI component.
- <p>[<u><font color="#008000">Deleted item</font></u>] <a name="Improve support for cheat sheets"><b>Improve
- support for cheat sheets</b></a><b>.</b> In Eclipse SDK 1.0, the Welcome editor
- is an example of a cheat sheet. A cheat sheet is an instance of a simple kind
- of workflow support. We will continue to evolve the mechanisms behind cheat
- sheets, including adding standard API for creating actions. These changes
- will affect the UI component. [<font color="#008000"><u>This has turned out
- to require a major effort, so we are removing this uncommitted item from the
- 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide project interchange mechanism">Provide
- project interchange mechanism</a>.</b> We will provide a way to export the
- resources in one of more workspace projects to an archive file that it can
- be saved for posterity or imported to another workspace. This affects the
- Core and UI components. [<font color="#008000"><u>A consequence of the
- new VCM story is that we do not need to provide a special mechanism for project
- interchange. Therefore we are removing this uncommitted item from the 2.0
- plan.</u></font>]
- <p>[<u><font color="#008000">Deleted item</font></u>] <b><a name="Provide additional internationalization support">Provide
- additional internationalization support</a>.</b> We will enable the
- Eclipse Platform to provide internationalization support for additional locales
- on some Motif operating environments. This affects the SWT component. [<font color="#008000"><u>We
- have added support for additional locales (see the Internationalization section
- in this plan for more details). This uncommitted item is redundant,
- so we are removing it from the 2.0 plan.</u></font>]
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Improve local resource history">Improve
- local resource history</a>.</b> The workspace local resource history mechanism
- keeps recent copies of modified or deleted files in order to help save the
- user from losing data in common situations. In 1.0, many UI actions that the
- user would reasonably expect to grow the history are not doing so, and there
- is no obvious way to recover a saved state of a file once it has been deleted.
- We plan to make the history facility more reliable and helpful for 2.0.
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Add ftp repository support">Add
- ftp repository support</a>.</b> We plan to build a simple repository adapter
- for ftp servers. This also affects the Core component (target management API).</p>
-</ul>
-
-
-
-<p>(End of items for Eclipse Platform subproject.)
-
-
-
-<h3>
-
-<a name="Java development tooling (JDT) subproject">Java development tooling (JDT) subproject</a></h3>
-
-<a href="http://www.eclipse.org/jdt/index.html">
-
-Java development tooling</a> (JDT) implements a Java IDE based on the Eclipse
-
-Platform.
-
-The following committed items reflect new features of JDT, or areas where existing
-
-features will be significantly reworked.
-
-<blockquote><a name="Reduce memory footprint for Java builder"><b>Reduce
-
-memory footprint for Java builder</b></a><b>.</b> The internal data structures of
-
-the Java incremental compilation mechanism is using more memory than necessary
-
-or reasonable. By fundamentally changing the approach to how incremental
-
-builds are done we expect to substantially reduce the memory footprint
-
-without significantly increasing incremental compile times.
-
-<p><b><a name="Improve Java search">Improve Java search</a>.</b> Java reference
-
-searches in Eclipse SDK 1.0 are limited to named types in source files. This
-
-will be addresses so to make it possible to find references in JAR libraries, and to distinguish read and write accesses to fields.
-
- <p><a name="Improve code assist"><b>Improve code assist</b></a><b>.</b> A number
-
-of changes will improve usability of code assist: including method argument
-
-names and types as hints; suggesting variable names; honoring visibility
-
-constraints dictated by the context.
-
-<p><b><a name="Upgrade Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform">Upgrade
-
-Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform</a>.</b>
-
-A new assertion feature was added in 1.4, and there were a few clarifications
-
-in obscure corners of the Java language specification. The Eclipse Java compiler
-
-will be upgraded to support 1.4, but will continue to support 1.3 via an option
-
-setting.
-
-<p><b><a name="Improve build classpath">Improve build classpath</a>.</b>
-
-By adding a mechanism for explicitly exporting libraries on a project's
-
-build classpath to downstream projects, it becomes possible to have a library
-
-project (one with a JAR and no source folder) that can stand in for a project
-
-containing source code. This change enables large scale development where
-
-source code is contained in multiple, related Java projects, by providing
-
-possibilities other than having all the source code projects in the workspace
-
-at all times (expensive to build). Plug-in development is a direct beneficiary.
-
- <p><b><a name="Improve accessibility - JDT">Improve accessibility</a>.</b> Applications
-
- selling to the US Government market are required by law to meet minimum accessibility
-
- guidelines (<a href="http://www.section508.gov/" target="_top">Section 508</a>).
-
- The JDT UI must meet minimum accessibility guidelines, and enable its client
-
- plug-ins to meet accessibility guidelines as well.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <a name="Improve Java editor"><b>Improve Java editor</b></a>. Rework
-
-menu bar contributions and context menu to improve usability; add a template
-
- facility with variable substitution; add navigation to a method's super
-
- implementation; add bracket matching; add error clueing; add line/column
- numbers.
-
-<p><b><a name="Improve refactoring">Improve refactoring</a>.</b>
-
-Implement additional refactorings: extract variable, inline temporary, push-up
-
-field/method, change method signature. Support reference updates in strings and
-
-comments for move/rename refactorings.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Improve refactoring">Improve package
-
-browsing</a></b>: Provide a more package-centric view for browsing. In 1.0, the
-
-Packages view presents packages grouped by their containers. We will continue to
-support the existing container based presentation; in addition, we are exploring
-alternatives. We
-
-will also add
-
-support to show the structure of a compilation unit in the Packages
-
-view.
-
-<p><b><a name="Facilitate string externalization">Facilitate
-
-</a><a name="Facilitate string externalization">string
-
-externalization</a></b><b>.</b> Add a wizard that
-
-allows the user to
-
-externalizing string literals in Java source code into standard Java resource bundles.
-
-<p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Allow runtime parameters to the configured">Allow runtime
-parameters to the configured</a>.</b> Using the new launch configuration mechanism
-
-provided by the Platform Debug component will allow the working directory, runtime classpath,
-
-boot classpath, extension directories, and other VM-type specific launch
-
-parameters to be configured.
-
- <p>[<u><font color="#008000">Revised item</font></u>] <b><a name="Support hot code replace when debugging JDK 1.4 targets">Support
- hot code replace when debugging compliant Java 1.4 targets</a>.</b> JDPA for
- version 1.4 of the Java 2 Platform allow a class to be updated while under
- the control of the debugger. In 1.0, this kind of support was only available
- for IBM J9 targets. The Java debugger will be changed to support both.
- Provide smart drop to frame that only removes affected frames from the stack.
- <p><b><a name="Enable JSP debugging with JPDA">Enable JSP debugging
-
-with JPDA</a>.</b> The Java debugger will enable JSP debugging via a flexible source lookup algorithm and breakpoint setting mechanism.
-
-<p><a name="Add debugger support for step filtering"><b>Add debugger
-
-support for step filtering</b></a><b>.</b> The Java debugger will avoid stepping into
-
-any class mentioned on a user-specified exclusion list.
-
-<p><b><a name="Improve data inspectors">Improve data inspectors</a>.</b> We will
-
-improve support in the debugger for inspecting objects, including running an
-
-object's toString method to obtain a readable string that may be more
-
-meaningful to the user.
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Add API for Java abstract syntax tree"><b>Add
-
-API for Java abstract syntax tree</b></a><b>.</b> In Eclipse SDK 1.0, refactoring uses
-
-compiler internals for parsing and walking the abstract syntax trees (ASTs)
-
-for Java source code. We will add API for creating and manipulating ASTs
-
-that can serve as the basis for other clients like refactoring. </p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <b><a name="Add field watchpoints">Support field
-
- watchpoints</a>.</b> We will add debugger support for field watchpoints.</p>
-
- <p>[<u><font color="#008000">Previously uncommitted item</font></u>] <a name="Improve Java editor"><b>Support editor key bindings</b></a>. Add support for user-configurable key
-
- bindings in the Java editor. This requires changes in the Platform UI
-
- component.<p>[<u><font color="#008000">New item</font></u>] <b><a name="Add support for JUnit">Add
- support for JUnit</a>.</b> We will include special tooling for the popular <a href="http://www.junit.org/">JUnit
- unit test framework</a> to facilitate authoring and running of JUnit test
- cases.<p>[<u><font color="#008000">New
- item</font></u>] <b><a name="Add support for Javadoc generation">Add support for Javadoc
- generation</a>.</b> We will add an action for generating Javadoc for a Java
- project (note: requires a standard JDK).<p>[<u><font color="#008000">New
- item</font></u>] <b>Improve navigating to Javadoc.</b>
- We will add quick keyboard navigation from names in Java source code to the
- corresponding Javadoc, including the API Javadoc for names declared in
- libraries.</blockquote>
-
-
-
-<h4>
-
-<a name="Uncommitted Items">
-
-Uncommitted Items</a> (Eclipse JDT subproject)</h4>
-
-<p><i>N.B. The following is the list of important JDT subproject work items
-
-which we are presently unable to commit to for the 2.0 release. Wherever
-
-possible, we will try to complete these items. Depending on how things work out,
-
-we should be able complete some of them. However, we cannot promise that we will
-
-complete any of them, and it would be unwise to gamble otherwise. Items not
-
-completed for 2.0 will carry over to the planning of the next release. We will
-
-revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-
-
-
-<blockquote>
- <p> <a name="Add conditional breakpoints"><b>Support conditional
-
- breakpoints</b></a><b>.</b> We will add debugger support
-
- for conditional breakpoints
-
-with simple conditions, including simply object identity tests of the form
-
- "this == id" sufficient for object breakpoints.</p>
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse JDT subproject.)
-
-
-
-<h3>
-
-<a name="Plug-in development environment (PDE) subproject">Plug-in development environment (PDE) subproject</a></h3>
-
-The <a href="http://www.eclipse.org/pde/index.html"> plug-in development environment</a>
-(PDE) consists of tools for developing plug-ins for the Eclipse Platform.
-For 2.0, the goal is to maintain the level of PDE support present in 1.0 while
-adding the necessary extensions that allow it to be the tool of choice for self-hosted
-Eclipse Project development. The following items are committed for 2.0:
-<blockquote> <b><a name="Improve accessibility - PDE">Improve accessibility</a>.</b>
-
- Applications selling to the US Government market are required by law to meet
-
- minimum accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
-
- 508</a>). The PDE UI must meet minimum accessibility guidelines, and enable
-
- its client plug-ins to meet accessibility guidelines as well.
-
- <p><b><a name="Support revamped install and update story">Support
-
- revamped install and update story</a>.</b> PDE contains support for building
-
- the deployable form of a plug-in, or set of plug-ins. We will update PDE to
-
- support the revised install and update story.</p>
-
- <p><b><a name="Improve support for large scale multi-project plug-in development">Improve
-
- support for large scale multi-project plug-in development</a>.</b> We will improve support
-
- for large scale development efforts involving multiple plug-ins spread across
-
- several projects in the workspace.</p>
-
- <p>[<u><font color="#008000">New item</font></u>] <b><a name="Provide PDE API">Provide
- PDE API</a>.</b> We will add an extension point to allow plug-ins to
- contribute wizards from creating new extensions in the PDE Plug-in Manifest
- editor, and expose PDE API needed by clients that provide such wizards. <p>[<u><font color="#008000">New item</font></u>]
- <b><a name="Source builds">Source builds</a>.</b> In 1.0, the process used to
- create new Eclipse SDK drops from sources is only usable by the original
- development team. In 2.0, the magic will be removed and replaced by
- generally available scripts that anyone can use to build Eclipse SDK
- drops from sources.
-
-</blockquote>
-
-
-
-<p>(End of items for Eclipse PDE subproject.)
-
-</body>
-
-</html>
-
diff --git a/eclipse_project_plan_2_0_rev1221.html b/eclipse_project_plan_2_0_rev1221.html
deleted file mode 100644
index f7a7fa6..0000000
--- a/eclipse_project_plan_2_0_rev1221.html
+++ /dev/null
@@ -1,707 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
- <meta name="Author" content="Eclipse Project PMC">
- <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
- <meta name="ProgId" content="FrontPage.Editor.Document">
- <title>Eclipse Project 2.0 Plan</title>
- <link rel="stylesheet" href="../default_style.css" type="text/css">
-</head>
-<body>
-
-<h1>
-Eclipse Project<br>
-DRAFT 2.0 Plan</h1>
-Last revised Friday, December 21, 2001
-<blockquote>
- <p><i>Please send comments about this draft plan to the </i><a href="mailto:eclipse-dev@eclipse.org">eclipse-dev@eclipse.org</a>
- <i>developer mailing list.</i></p>
-</blockquote>
-<p>This document lays out the plan for the next major release of the Eclipse
-Project, designated release 2.0. The main emphasis of the Eclipse 2.0 release will be
-on improving quality
-(bug fixing) and performance, with a lesser emphasis on adding new features and APIs.
-<p>This plan serves at least two purposes. First, it serves as the blueprint guiding
-the efforts of the developers working on the Eclipse subprojects. The work items
-committed in this plan were selected over all others because they were judged to
-provide the most value to customers for this follow-on to the Eclipse 1.0
-release. Second, this plan serves as an important input to the planning processes
-of the various customers of the Eclipse Platform. This plan tells them what to
-expect (or what not to expect) in the next release so that they can plan their
-projects accordingly.
-<p>Plans are rarely completely unchanging over the life cycle of a release, and
- this project is no exception. We will update this document as required to reflect
- any changes to the 2.0 release plan. While we certainly do not expect to backtrack
- on items already committed, we do anticipate adding further committed items
- to the list. This plan already includes a number of extra work items which we
- are presently unable to commit to for the 2.0 release due to time, but which
- are nonetheless worthy of being solved. Where possible, we will try to complete
- these items, and will revise this plan as soon as we know we can make a definite
- commitment. The individual Eclipse <a href="http://www.eclipse.org/eclipse/index.html" target="_top">subproject
- and component web pages</a> and <a href="http://www.eclipse.org/mail/index.html" target="_top">developer
- mailing list archives</a> contain further, in-depth information about how a
- component is changing. Particular problem reports being worked on for the 2.0
- release can be tracked through the Eclipse <a href="http://dev.eclipse.org/bugs/">bug
- database</a>; the "Target Milestone" field reflects when a work item
- will become available in the main development stream.
-<h2>Release deliverables</h2>
-<p>The release deliverables are:
-<ul>
- <li>Source code release for Eclipse project, available
- as versions tagged "R2_0" in the Eclipse <a href="http://dev.eclipse.org/viewcvs/">CVS
- repository</a>.</li>
- <li>Eclipse project SDK (includes Platform, JDT, and PDE source zips)
- (downloadable).</li>
- <li>Eclipse Platform runtime binary distribution (downloadable).</li>
- <li>JDT runtime binary distribution (downloadable).</li>
- <li>Eclipse Examples (downloadable).</li>
-</ul>
-<h2>Release milestones</h2>
-<p>The release milestones are:</p>
-<ul>
- <li>December 7, 2001 - milestone 0 - stable build reflecting progress</li>
- <li>December 21, 2001 - milestone 1 - stable build reflecting good progress</li>
- <li>January 25, 2002 - milestone 2 - stable build reflecting significant
- progress</li>
- <li>February 15, 2002 - milestone 3 - stable build - feature complete -
- initial development freeze</li>
-</ul>
-The 2.0 release is targeted for April 2002. All release deliverables will be available for download
-as soon as the release has been tested and validated in the target operating
-configurations listed below.
-<h2>
-Target Operating Environments</h2>
-
-<p>Most of Eclipse is "pure" Java and has no direct dependence on the underlying
-operating system. The chief dependence is therefore on the Java 2 Platform
-itself. The 2.0 release of the Eclipse project will be written against version
-1.3 of the Java 2 Platform APIs, and targeted to run on either version
-1.3 or 1.4 of the Java 2 Runtime Environment, Standard Edition.</p>
-<p>We plan to test and validate Eclipse 2.0 on the most up-to-date Java 2
-Platform implementations available. These are:</p>
-<table border="1" width="91%">
- <tr>
- <td width="19%"><b>Operating system</b></td>
- <td width="24%"><b>Processor architecture</b></td>
- <td width="73%"><b>Java 2 Platforms</b></td>
- </tr>
- <tr>
- <td width="19%" rowspan="3">Microsoft<br>
- Windows</td>
- <td width="24%" rowspan="3">Intel x86</td>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for
- Microsoft Windows</td>
- </tr>
- <tr>
- <td width="73%">IBM Developer Kit for Windows, Java 2 Technology Edition, version 1.3.0</td>
- </tr>
- <tr>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for
- Microsoft Windows (currently in beta)</td>
- </tr>
- <tr>
- <td width="19%" rowspan="3">Linux</td>
- <td width="24%" rowspan="3">Intel x86</td>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Linux x86</td>
- </tr>
- <tr>
- <td width="73%">IBM Developer Kit for Linux, Java 2 Technology Edition, version 1.3.0</td>
- </tr>
- <tr>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Linux x86
- (currently in beta)</td>
- </tr>
- <tr>
- <td width="19%" rowspan="2">Sun Solaris</td>
- <td width="24%" rowspan="2">SPARC</td>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.3.1 for Solaris
- SPARC</td>
- </tr>
- <tr>
- <td width="73%">Sun Java 2 SDK, Standard Edition, version 1.4 for Solaris
- SPARC (currently in beta)</td>
- </tr>
- <tr>
- <td width="19%">HP HP-UX</td>
- <td width="24%">hp9000 PA-RISC</td>
- <td width="73%"><span class="header">HP-UX SDK for the Java 2 platform,
- version 1.3.1 for hp9000 PA-RISC</span></td>
- </tr>
- <tr>
- <td width="19%">IBM AIX</td>
- <td width="24%">PowerPC</td>
- <td width="73%">IBM Developer Kit for AIX, Java 2 Technology Edition, version 1.3.0</td>
- </tr>
-</table>
-<p><span class="header">The following table describes the combinations of
-operating system and Java 2 Platform used when testing the Eclipse
-configurations. The status column indicates the level of testing: Primary means
-a full tested configuration; </span>Secondary means a configuration which is
-only lightly tested; Untested means a configuration that has received no
-testing, but which should work. Note that the Linux GTK configuration is
-considered early access for the 2.0 release; it will be tested, but it is known
-in advance that it will not be of product quality in this release.</p>
-<table border="1" width="91%">
- <tr>
- <td width="11%"><b>Window system</b></td>
- <td width="28%"><b>Java 2 Platform<br>
- (see above table)</b></td>
- <td width="42%"><b>Operating Environment</b></td>
- <td width="19%"><b>Testing Status</b></td>
- </tr>
- <tr>
- <td width="11%" rowspan="5">Win32</td>
- <td width="28%" rowspan="5">Windows on Intel x86</td>
- <td width="42%">Windows 2000</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="42%">Windows XP</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="42%">Windows ME</td>
- <td width="19%">Secondary</td>
- </tr>
- <tr>
- <td width="42%">Windows 98SE</td>
- <td width="19%">Secondary</td>
- </tr>
- <tr>
- <td width="42%">Windows NT</td>
- <td width="19%">Secondary</td>
- </tr>
- <tr>
- <td width="11%" rowspan="6">Motif</td>
- <td width="28%" rowspan="3">
- <p>Linux on Intel x86</p>
- <p> </td>
- <td width="42%">RedHat Linux 7.2 x86</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="42%">
-SuSE Linux 7.3 x86</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="42%">Other Linux; kernel version 2.4.7, and XFree86 version 4.1.0</td>
- <td width="19%">Untested</td>
- </tr>
- <tr>
- <td width="28%">Solaris on SPARC </td>
- <td width="42%">Sun Solaris 8 SPARC</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="28%">HP-UX on hp9000 PA-RISC</td>
- <td width="42%">HP-UX 11i hp9000</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="28%">AIX on PowerPC</td>
- <td width="42%">IBM
-AIX 5.1 on PowerPC</td>
- <td width="19%">Primary</td>
- </tr>
- <tr>
- <td width="11%" rowspan="3">GTK</td>
- <td width="28%" rowspan="3">Linux on Intel x86</td>
- <td width="42%">RedHat Linux 7.2 x86</td>
- <td width="19%"><i>Early access</i></td>
- </tr>
- <tr>
- <td width="42%">
-SuSE Linux 7.3 x86</td>
- <td width="19%"><i>Early access</i></td>
- </tr>
- <tr>
- <td width="42%">Other Linux; kernel version 2.4.7, and GTK version 1.2.8,
- 1.2.9, or 1.2.10</td>
- <td width="19%"><i>Early access; untested</i></td>
- </tr>
-</table>
-<h4>
-Internationalization</h4>
-<p>
-The Eclipse Platform is designed as the basis for internationalized products.
-The user interface elements provided by the Eclipse components, including
-dialogs and error messages, are externalized. The English strings are provided
-as the default resource bundles.</p>
-
-<p>We will perform basic tests in German and Japanese locales.
-<p>IMPORTANT: Internationalization is supported only on Windows platforms in the
- 2.0 release. (See the <a href="#Uncommitted Items">Eclipse Platform
-uncommitted items</a> for additional work in this area.)
-<h4>
-BIDI support</h4>
-<p> Eclipse is a platform for building development environments targeted at technical
- professionals. Eclipse 2.0 will permit technical professionals who are working
- in English to build Hebrew/Arabic end-user applications.</p>
-<p>IMPORTANT: BIDI is supported only on Windows platforms in the 2.0 release.</p>
-<h2>
-Compatibility with Previous Release</h2>
-Eclipse 2.0 will be upwards compatible with Eclipse 1.0 to the
-greatest extent possible. We anticipate a small number of areas where slavishly
-maintaining compatibility would not be in the best interests of the Platform
-or its clients. All such exceptions will be noted in the 2.0 release
-notes so that clients can assess the impact of these changes on their plug-ins
-and products.<p><b>Status of interim 1.0 APIs and plug-ins</b>: Some of the
-Eclipse APIs and plug-ins in 1.0 were marked as provisional (debug, for
-instance). These APIs and plug-ins will either appear in stable, finished form in
-the 2.0 release, or be removed (with the exception of Scripting). As anticipated
-(and advertised), these API changes will likely break 1.0 client plug-ins that
-made use of that particular API in its early form. Even if code appears to work
-with 2.0, it would still need to be completely reviewed to ensure that it abides
-by the final API contracts.</p>
-<p><b>API Contract Compatibility:</b> Eclipse 2.0 will be upwards
-contract-compatible with Eclipse 1.0 unless noted. This means that
-programs in full compliance with contracts specified in the Eclipse 1.0
-APIs will automatically be in full compliance with the Eclipse 2.0 APIs. (API is
-construed broadly to include such things as plug-in extension points.) Downward contract compatibility is not supported. There is no guarantee
-that compliance with the Eclipse 2.0 APIs would ensure compliance with
-the Eclipse 1.0 APIs.
-<p><b>Binary (plug-in) Compatibility:</b> Eclipse 2.0 will be upwards
-binary-compatible
-with Eclipse 1.0 unless noted. This means that plug-ins built for Eclipse
-1.0 will continue to work correctly in Eclipse 2.0 without change. Downward
-plug-in compatibility is not supported. Plug-ins for Eclipse
-2.0 are unlikely to be usable in Eclipse 1.0. Plug-ins with hard-coded
-references in their plug-in manifest file to 1.0 versions of prerequisite
-Eclipse project plug-ins will not work in 2.0 as the plug-in version numbers
-will be incompatible.
-<p><b>Source Compatibility:</b> Eclipse 2.0 will be upwards source-compatible
-with Eclipse 1.0 unless noted. This means that source files written
-to use Eclipse 1.0 APIs can be successfully compiled and run against the
-Eclipse 2.0 APIs. Since source incompatibilities are easy to deal with,
-maintaining source compatibility is considered much less important than
-maintaining contract and binary compatibility. Downward source compatibility is not supported. If source files use
-new Eclipse APIs, they will not be usable with an earlier version of Eclipse.
-<p><b>Workspace Compatibility:</b> Eclipse 2.0 will be upwards
-workspace-compatible with Eclipse 1.0 unless noted. This means that
-workspaces and projects created with Eclipse 1.0 can be successfully opened by Eclipse
-2.0 and upgraded to a 2.0 workspace. Individual plug-ins developed for
-Eclipse 1.0 should provide similar upwards compatibility for their workspace
-metadata; plug-in developers are responsible for ensuring that their plug-ins
-recognize 1.0 metadata and process it appropriately. Note: the interim
-Eclipse 1.0 plug-ins (ones with provisional APIs) are unlikely to automatically
-upgrade their metadata to 2.0. Downward workspace compatibility is not supported. A workspace created
-(or opened) by Eclipse 2.0 will be unusable with an earlier version
-of Eclipse.
-<p><b>Non-compliant usage of Eclipse</b>: All non-API methods and
-classes, and certainly everything in a package with "internal" in its name, are considered implementation details which may vary between operating
-environment and are subject to change without notice. Client plug-ins that
-directly depend on anything other than what is specified in the Eclipse API are
-inherently unsupportable and receive no guarantees about compatibility within a
-single release much less with an earlier release. Refer to <i><a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
-to Use the Eclipse API</a></i> for information
-about how to write compliant plug-ins.
-<h2>
-Eclipse Subprojects</h2>
-The Eclipse project consists of 3 subprojects. Each subproject
-is covered in its own section:
-<blockquote><font size=+0><a href="#Eclipse Platform subproject">Eclipse Platform</a></font>
-<br><font size=+0><a href="#Java development tooling (JDT) subproject">JDT - Java development tooling</a></font>
-<br><font size=+0><a href="#Plug-in development environment (PDE) subproject">PDE - Plug-in development environment</a></font></blockquote>
-<p>For each subproject, the items listed reflect new features of the Eclipse
-platform, or areas where existing features will be significantly reworked.
-Each item indicates the component affected by that work item (many items
-involve coordinated changes to several components).
-<p>Note that fixing bugs, improving test coverage, documentation, examples,
-etc. are considered routine ongoing maintenance activities and are not
-included in this plan unless they would also involve significant changes to the Platform.
-<h3>
-<a name="Eclipse Platform subproject">Eclipse Platform subproject</a></h3>
-The following items reflect new features of the Eclipse platform, or areas
-where existing features will be significantly reworked. Each item indicates
-the component affected by that work item (some items involve coordinated
-changes to several components). Additional uncommitted items affecting these
-components are listed in the <a href="#Uncommitted Items">Uncommitted Items</a>
-section at the end.
-<h4>
-Platform Core component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/main.html">Platform
-Core component</a> covers most of the Platform's non-UI infrastructure,
-including the basic plug-in mechanism, resources in the workspace. The following
-items are committed for 2.0:
-<blockquote><b><a name="Improve Platform startup times">Improve Platform
-startup times</a>.</b> Eclipse Platform startup times 1.0 reflect the speed of XML parsing for plug-in manifest files. As the sheer number of available
-plug-ins can be expected to increase by an order of magnitude in the near future,
-we need a more scalable solution to this problem. A likely improvement in startup
-time will come with computing and caching the plug-in registry on disk.
-<p><a name="Improve Ant integration"><b>Provide first-class Ant integration</b></a><b>.</b>
- In 1.0, Ant was a second-class Eclipse citizen. We plan to significantly increase the Platform's
-power and flexibility by connecting it to the Platform's build story. These changes will likely impact the UI component
-as well.
-<p><a name="Improve serviceability"><b>Improve serviceability</b></a><b>.</b>
-Several factors make it difficult in 1.0 to debug an Eclipse Platform that
-is failing in the field: startup failures are poorly diagnosed; error messages in the log sometimes contain little
-or no useful information; the internal plug-in log file is busy while the
-Platform is running, and gets erased as soon as the Platform is restarted.
-We plan to improve the startup sequence, eliminate unhelpful error messages, take steps to help identify
-which plug-in is the apparent source of an internal error, and ensure that
-the information in the internal logs is more readily accessible. These changes will
-also impact the UI component.</blockquote>
-
-<h4>
-Installation and Update component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/main.html"> Installation and Update component</a> is responsible for installing and upgrading the Eclipse
-Platform in the field. Eclipse 1.0 contains an early version
-of this component; it will be thoroughly reworked for 2.0. The following items
-are committed for 2.0:
-<blockquote>
- <p><b><a name="Redesign plug-in install and update story">Redesign
-plug-in installation and update story</a>.</b> The 1.0 concepts of <i>component</i>
- and <i>configuration</i> will be replaced with a new concept called a <i>feature</i>.
- Features define the packaging structure for a group of related plug-ins,
- plug-in fragments, and optionally non-plug-in files. This change impacts the Core
-component and the PDE subproject as well.</p>
- <p><b><a name="Improve installer flexiblilty">Improve installer </a><a name="Improve installer flexiblilty">flexibility</a>.</b>
- The standard Platform installer will be more flexible and support alternate
- packaging and site management schemes: structured site map for discovering
- available updates; improved granularity of downloads; accommodate native
- installers; feature-specific custom installers packaged with feature and
- executed during feature installation.</p>
-</blockquote>
-
-<h4>
-Platform UI component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/main.html">Platform
-UI component</a> provides the generic workbench UI for the Eclipse Platform. The following
-items are committed for 2.0:
-<blockquote><b><a name="Improve accessibility - UI">Improve accessibility</a>.</b>
- Applications selling to the US Government market are required to meet minimum
- accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
- 508</a>). The workbench and its standard views and wizards must meet minimum
- accessibility guidelines, including mouse-less operation. The Eclipse Platform
- needs to enable other client plug-ins to meet accessibility guidelines too.
- This change also impacts the SWT component.
- <p><b><a NAME="Improve editor management">Improve editor management</a>.</b>
-Users are finding it difficult to work with many editors open simultaneously
-in the Eclipse 1.0 workbench, all seemingly stemming from the way editors
-are currently managed. The workbench's approach to editor management will
-be reviewed and revised to improve usability.
-<p><b><a name="Improve interaction between editors and views">Improve
-interaction between editors and views</a>.</b> There are some unfortunate interactions
-between editors and views in Eclipse 1.0 that make it difficult for views
-to serve as "secondary windows" to an editor. Among other things, this
-leads to poor integration of standard views. The workbench's current approach
-to editors and views will be reviewed and revised to facilitate interaction
-and improve integration.
-<p><b><a name="Allow context menu contributions in Outline view">Allow
-context menu contributions in Outline view</a>.</b> In Eclipse 1.0, clients
-have no control over the standard Outline view's popup context menu. This
-will be addressed so that clients will be able to make contributions to
-this menu.
-<p><b><a name="Improve usability re: losing context">Improve usability
-re: losing context</a>.</b> Some users have reported getting lost in the UI
-and having to close all open editors and perspectives to get their workbench
-back into a familiar state. The current approach will be reviewed and revised
-to improve usability.
-<p><b><a name="Improve the Task view">Improve the Task view</a>.</b> The
-standard Task view will be improved in the following areas: performance and
-usability for large numbers of items in the view; context-sensitive help; and
-making contributions to the view's context menu.<p><b><a name="Add support for working sets">Add support for working
- sets</a>.</b> In 1.0, all resources in the workspace are equally accessible.
- The workbench will let the user define working sets of resources, suitable for
- providing more restricted contexts for browsing, searching, and the like.</blockquote>
-
-<h4>
-SWT component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/main.html">SWT
-component</a> is the low-level widget toolkit used in Eclipse. The following
-items are committed for 2.0:
-<blockquote>
- <p><b><a name="Port to other window systems">Support additional window
- systems</a>.</b> Add support for new window system: GTK. Port Motif-based
- implementation to other operating systems: AIX, HP-UX, Solaris. Foster and
- encourage efforts to port to other window systems.
- <p><a name="Support GB18030"><b>Support GB18030</b></a><b>.</b> GB 18030
-is a new Chinese code page standard. Products shipping into the China market
-are required to support this new standard. We believe that Eclipse itself
- requires no specific changes to support GB 18030, but is entirely dependent on
- the Java 2 Runtime Environment to provide the necessary locale and character
- encoding support. The GB18030 character encoding is not supported in version
- 1.3 of Java 2 Platform, but is included in version 1.4.<p><b><a name="Utilize native Unicode support">Utilize
- Windows native Unicode support</a>.</b> The SWT implementation will use
- native Unicode support on all Windows operating systems that support it (NT,
- 2000, XP).<p><b>Improve Motif appearance and performance.</b> In 1.0,
- support for the Motif window system lags behind that of Windows. We plan to improve the
- appearance and performance of SWT on Motif.
-</blockquote>
-
-<h4>
-VCM component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/main.html"> VCM component</a> provides version and configuration management for projects
-in the workspace and attendant team support. The following items are committed for 2.0:
-<blockquote><a name="Provide VCM API"><b>Provide an open VCM </b></a><b><a name="Provide VCM API">story</a>.</b> Eclipse
-1.0 includes CVS repository support, but has no official VCM API that allows
-other version and configuration management systems to integrate into the
-Platform. We will provide a simple API, extension points, and usage guidelines
-so that VCM providers can adapt their repositories and integrate VCM product-specific
-UI elements into the Eclipse UI.
-<p><a name="Improve CVS repository integration"><b>Improve CVS repository
-integration</b></a><b>.</b> In addition to converting the existing CVS repository
-adapter to the new VCM API, CVS support will be improved, including: support
-for CVS modules so that Eclipse can be connected to existing CVS repositories;
-support for CVS patch facility so that CVS users can capture changes to
-a project in a tangible form that can be submitted to others or archived
-(this also involves the compare infrastructure).</blockquote>
-
-<ul><a name="Add mechanism for validating edits and saves"><b>Add mechanism
-for validating edits and saves</b></a><b>.</b> Some VCM providers require a "heads up" when the user starts
-to change the contents of a file open in an editor (e.g., to allow the file to
- be checked out and locked), or when the user is about to save the changed contents
-back to disk. We will add a callback so that the relevant VCM provider will be
- able to register for advance notification with an opportunity to veto. This
- change also affects the UI and Core components.<p><b>Add non-versioning WebDAV repository support.</b>
- We plan to build a simple repository adapter for non-versioning WebDAV
- servers. This will allow users to share their files via any WebDAV compliant
- server. This also affects the Core component (target management API).</p>
-</ul>
-
-<h4>
-Help component</h4>
-
-<p>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-home/main.html"> Help component</a> organizes help contributions and presents them to the
-user. The following items are committed for 2.0:</p>
-<blockquote><p><b><a name="Simplify contribution mechanism">Simplify
- contribution mechanism</a>.</b> Based on feedback on 1.0, we plan to rework
- and simplify the help contribution mechanism. Online documentation created for 1.0 will
- need to be converted for 2.0.<p><a name="Use a separate web browser to present help"><b>Use
-a separate web browser to present help</b></a><b>.</b> We will use an external
- web browser launched in a separate window to <br>
- present all documentation and online help. This will allow help to be presented in a non-modal way.<p><b><a name="Support live help">Support
- live help</a>.</b> We will support the ability to trigger developer-supplied
- actions as a result of navigating a link in the online documentation. The actions will execute within the Eclipse environment.
-<p><b><a name="Allow remote help content">Enable help server</a>s.</b> We will support configurations where help can be served up to an Eclipse client by a remote web <br>
-server (the server must support servlets).
-<p><b><a name="Support standalone help">Support standalone help</a>.</b> Developers will be able to reuse the Eclipse help function even in products that are not built using the Eclipse technology. We will provide for both in-process and command-line invocation of this support.
-<p><b><a name=""Info Center" support">"Info Center" support</a>.</b> It is often desirable to be able to provide plug-in documentation that is accessible to users that do not have Eclipse installed. We will support configurations where online documentation can be hosted on a web server
-and viewed through a regular web browser.
-</blockquote>
-
-<h4>
-Platform Debug component</h4>
-The <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-debug-home/main.html">Platform
-Debug component</a> provides generic Core and UI for launching, running, and debugging
-programs. The following items are committed for 2.0:
-<blockquote><a name="Stabilize Debug API"><b>Stabilize Debug API</b></a><b>.</b>
-In Eclipse 1.0, all debug APIs were considered provisional and incomplete.
-The Debug APIs will appear in finished, stable form.</blockquote>
-
-<blockquote><a name="Add support for debugging procedural languages"><b>Add
-support for debugging procedural languages</b></a><b>.</b> The Debug component will be extended to
- enable debuggers to be written for procedural languages (e.g., C) which get compiled to machine code and run
-on standard hardware.
-<p><a name="Add launch configurations"><b>Add launch configurations</b></a><b>.</b>
-The Debug component will add a general mechanism and UI for the user to define launch
-configurations describing how something is to be launched (e.g., command
-line options).</blockquote>
-
-<h4>
-<a name="Uncommitted Items">
-Uncommitted Items</a> (Eclipse Platform subproject)</h4>
-<p><i>N.B. The following is the list of important Eclipse subproject work items
-which we are presently unable to commit to for the 2.0 release. Wherever
-possible, we will try to complete these items. Depending on how things work out,
-we should be able complete some of them. However, we cannot promise that we will
-complete any of them, and it would be unwise to gamble otherwise. Items not
-completed for 2.0 will carry over to the planning of the next release. We will
-revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-<ul>
-<p><a name="Add support for non-local files"><b>Add
-support for non-local files</b></a><b>.</b> It is expensive to set up a workspace
-project containing a large number of files that normally reside on remote
-server or file system. Core has a basic mechanism that permits the workspace
-to contain placeholders for files and folders necessarily resident in the
-local file system. The Core mechanism will be augmented so that VCM can
-use it to hook it to retrieve files from a remote server or file system
-on demand. The UI component is also affected.
-<p><a name="Improve usability of project natures"><b>Improve
-usability of project natures</b></a><b>.</b> In Eclipse 1.0, project natures are secretly
-configured by the plug-ins that define them, leading to problems and blind
-spots when projects have other natures as well. We will review and revise
-the approach to how project natures are used, presented, and manipulated. These
-changes will affect the UI and Core components.
-<p><a name="Improve consistency of saving workbench state"><b>Improve
-consistency of saving workbench state</b></a><b>.</b> In Eclipse 1.0, there are a
-number of instances where user-configurable UI settings are not being persisted
-between sessions. The UI will provide better support for saving important
-UI state.
-<p><a name="Improve undo/redo in workbench"><b>Improve
-undo/redo in workbench</b></a><b>.</b> In Eclipse 1.0, undo and redo are poorly supported
-for workbench actions, and it is still far too easy for a user to lose
-work. We will consider providing an undo/redo service that will help decrease
-the risk of inadvertently losing work. These changes will affect the UI
-component.
-<p><a name="Provide a standard Console view"><b>Provide
-a standard Console view</b></a><b>.</b> In Eclipse 1.0, there is a proliferation of
-consoles furnished by clients (including JDT, PDE, Ant). The workbench
-will supply a standard Console view; clients will be encouraged to use
-it instead of providing their own. These changes will affect the UI component.
-<p><a name="Improve support for cheat sheets"><b>Improve
-support for cheat sheets</b></a><b>.</b> In Eclipse 1.0,
-the Welcome editor is an example of a cheat sheet. A cheat sheet is an
-instance of a simple kind of workflow support. We will continue to evolve
-the mechanisms behind cheat sheets, including adding standard API for creating
-actions. These changes will affect the UI component.<p><b><a name="Allow pre-validation of rename/move/delete">Allow pre-validation of
- rename/move/delete</a>.</b> VCM providers that
- need to manage a project's namespace would like advance notification of
- impending resource moves, renames, and deletes. (Other clients would like a
- similar opportunity to veto inappropriate name changes to their resources;
- this is a different concern.) We will add a callback so that the
- relevant VCM provider will be able to register for advance notification with
- an opportunity to veto. These changes will affect the UI and Core components.
- <p><a name="Support unmanaged resources in managed projects"><b>Support
-unmanaged resources in managed projects</b></a><b>.</b> Workspace projects often contain
-files derived by processing other files; it is usually the case that these
-derived files should not be under VCM, even though the rest of the files
-in the project are. There needs to be some means of dealing with this;
-depending on the solution, this may require support from Core and UI.</p>
-<p><a name="Add search support"><b>Add help search support</b></a><b>.</b>
- We will provide the ability to search help documentation. This change will
-affect the Help component.<p><b><a name="Provide project interchange mechanism">Provide
-project interchange mechanism</a>.</b> We will provide a way to export the
-resources in one of more Eclipse workspace projects to an archive file that it
-can be saved for posterity or imported to another workspace. This affects the
-Core and UI components.<p><b><a name="Provide additional internationalization support">Provide
-additional internationalization support</a>.</b> We will enable the
-Eclipse Platform to provide internationalization support for additional locales
-on some Motif operating environments. This affects the SWT component.
-</ul>
-
-<p>(End of items for Eclipse Platform subproject.)
-
-<h3>
-<a name="Java development tooling (JDT) subproject">Java development tooling (JDT) subproject</a></h3>
-<a href="http://www.eclipse.org/jdt/index.html">
-Java development tooling</a> (JDT) implements a Java IDE based on the Eclipse
-Platform.
-The following committed items reflect new features of JDT, or areas where existing
-features will be significantly reworked.
-<blockquote><a name="Reduce memory footprint for Java builder"><b>Reduce
-memory footprint for Java builder</b></a><b>.</b> The internal data structures of
-the Java incremental compilation mechanism is using more memory than necessary
-or reasonable. By fundamentally changing the approach to how incremental
-builds are done we expect to substantially reduce the memory footprint
-without significantly increasing incremental compile times.
-<p><b><a name="Improve Java search">Improve Java search</a>.</b> Java reference
-searches in Eclipse 1.0 are limited to named types in source files. This
-will be addresses so to make it possible to find references in JAR libraries, and to distinguish read and write accesses to fields.
-<p><a name="Improve code assist"><b>Improve code assist</b></a><b>.</b> A number
-of changes will improve usability of code assist: including method argument
-names and types as hints; suggesting variable names; honoring visibility
-constraints dictated by the context.
-<p><b><a name="Upgrade Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform">Upgrade
-Eclipse Java compiler to be compliant with version 1.4 of the Java 2 Platform</a>.</b>
-A new assertion feature was added in 1.4, and there were a few clarifications
-in obscure corners of the Java language specification. The Eclipse Java compiler
-will be upgraded to support 1.4, but will continue to support 1.3 via an option
-setting.
-<p><b><a name="Improve build classpath">Improve build classpath</a>.</b>
-By adding a mechanism for explicitly exporting libraries on a project's
-build classpath to downstream projects, it becomes possible to have a library
-project (one with a JAR and no source folder) that can stand in for a project
-containing source code. This change enables large scale development where
-source code is contained in multiple, related Java projects, by providing
-possibilities other than having all the source code projects in the workspace
-at all times (expensive to build). Plug-in development is a direct beneficiary.
- <p><b><a name="Improve accessibility - JDT">Improve accessibility</a>.</b> Applications
- selling to the US Government market are required by law to meet minimum accessibility
- guidelines (<a href="http://www.section508.gov/" target="_top">Section 508</a>).
- The JDT UI must meet minimum accessibility guidelines, and enable its client
- plug-ins to meet accessibility guidelines as well.
- <p><a name="Improve Java editor"><b>Improve Java editor</b></a>. Rework
-menu bar contributions and context menu to improve usability; add a template
- facility with variable substitution; navigate to a method's super
- implementation; add bracket matching.
-<p><b><a name="Improve refactoring">Improve refactoring</a>.</b>
-Implement additional refactorings: extract variable, inline temporary, push-up
-field/method, change method signature. Support reference updates in strings and
-comments for move/rename refactorings.
-<p><b><a name="Improve refactoring">Improve package
-browsing</a></b>: Provide a more package centric-view for browsing. In 1.0, the
-Packages view presents packages grouped by their containers. We will add another
-presentation that shows packages independent of their physical containment. We
-will also add
-support to show the structure of a compilation unit in the Packages
-view.
-<p><b><a name="Facilitate string externalization">Facilitate
-</a><a name="Facilitate string externalization">string
-externalization</a></b><b>.</b> Add a wizard that
-allows the user to
-externalizing string literals in Java source code into standard Java resource bundles.
-<p><b><a name="Allow runtime classpath to the configured">Allow runtime
-classpath to the configured</a>.</b> Using the new launch configuration mechanism
-provided by the Platform Debug component will allow the runtime classpath,
-boot classpath, extension directories, and other VM-type specific launch
-parameters to be configured.
-<p><b><a name="Support hot code replace when debugging JDK 1.4 targets">Support hot code replace when
-debugging compliant JDK 1.4 targets</a>.</b> JDPA for version 1.4 of the Java
-2 Platform allow a class to be updated while under the control of the debugger.
-In 1.0, this kind of support was only available for IBM J9 targets. The Java debugger will
-be changed to support both.<p><b><a name="Enable JSP debugging with JPDA">Enable JSP debugging
-with JPDA</a>.</b> The Java debugger will enable JSP debugging via a flexible source lookup algorithm and breakpoint setting mechanism.
-<p><a name="Add debugger support for step filtering"><b>Add debugger
-support for step filtering</b></a><b>.</b> The Java debugger will avoid stepping into
-any class mentioned on a user-specified exclusion list.
-<p><b><a name="Improve data inspectors">Improve data inspectors</a>.</b> We will
-improve support in the debugger for inspecting objects, including running an
-object's toString method to obtain a readable string that may be more
-meaningful to the user.</blockquote>
-
-<h4>
-Uncommitted Items</h4>
-<p><i>N.B. The following is the list of important JDT subproject work items
-which we are presently unable to commit to for the 2.0 release. Wherever
-possible, we will try to complete these items. Depending on how things work out,
-we should be able complete some of them. However, we cannot promise that we will
-complete any of them, and it would be unwise to gamble otherwise. Items not
-completed for 2.0 will carry over to the planning of the next release. We will
-revise this 2.0 plan as soon as we can definitively commit to any of them.</i></p>
-<blockquote>
- <p><a name="Add API for Java abstract syntax tree"><b>Add
-API for Java abstract syntax tree</b></a><b>.</b> In Eclipse 1.0, refactoring uses
-compiler internals for parsing and walking the abstract syntax trees (ASTs)
-for Java source code. We will add API for creating and manipulating ASTs
-that can serve as the basis for other clients like refactoring. </p>
- <p><a name="Add conditional breakpoints"><b>Support conditional
- breakpoints</b></a><b>.</b> We will add debugger support
- for conditional breakpoints
-with simple conditions, including simply object identity tests of the form
- "this == id" sufficient for object breakpoints.</p>
- <p><b><a name="Add field watchpoints">Support field
- watchpoints</a>.</b> We will add debugger support for field watchpoints.</p>
- <p><a name="Improve Java editor"><b>Support editor key bindings</b></a>. Add support for user-configurable key
- bindings in the Java editor. This requires changes in the Platform UI
- component.
-</blockquote>
-
-<p>(End of items for Eclipse JDT subproject.)
-
-<h3>
-<a name="Plug-in development environment (PDE) subproject">Plug-in development environment (PDE) subproject</a></h3>
-The <a href="http://www.eclipse.org/pde/index.html"> plug-in development environment</a> (PDE) consists of Eclipse-based tools
-for developing Eclipse plug-ins. For 2.0, the goal is to maintain
-the level of PDE support present in 1.0 while adding the necessary extensions
-that allow it to be the tool of choice for self-hosted Eclipse project
-development. The following items are committed for 2.0:
-<blockquote> <b><a name="Improve accessibility - PDE">Improve accessibility</a>.</b>
- Applications selling to the US Government market are required by law to meet
- minimum accessibility guidelines (<a href="http://www.section508.gov/" target="_top">Section
- 508</a>). The PDE UI must meet minimum accessibility guidelines, and enable
- its client plug-ins to meet accessibility guidelines as well.
- <p><b><a name="Support revamped install and update story">Support
- revamped install and update story</a>.</b> PDE contains support for building
- the deployable form of a plug-in, or set of plug-ins. We will update PDE to
- support the revised install and update story.</p>
- <p><b><a name="Improve support for large scale multi-project plug-in development">Improve
- support for large scale multi-project plug-in development</a>.</b> We will improve support
- for large scale development efforts involving multiple plug-ins spread across
- several projects in the workspace.</p>
-</blockquote>
-</body>
-</html>
diff --git a/faq/default_style.css b/faq/default_style.css
deleted file mode 100644
index d725483..0000000
--- a/faq/default_style.css
+++ /dev/null
@@ -1,11 +0,0 @@
-p, table, td, th { font-family: arial, helvetica, geneva; font-size: 10pt}
-pre { font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code { font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup { font-family: arial,helvetica,geneva; font-size: 10px}
-h3 { font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li { font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 { font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body { font-family: arial, helvetica, geneva; font-size: 10pt; clip: rect( ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
diff --git a/faq/eclipse-faq.html b/faq/eclipse-faq.html
deleted file mode 100644
index 25e7564..0000000
--- a/faq/eclipse-faq.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<html>
- <head>
- <meta http-equiv="refresh" content="2; url=http://wiki.eclipse.org/index.php/Eclipse_FAQs" />
- </head>
- <body>
- <a href="http://wiki.eclipse.org/index.php/Eclipse_FAQs">This page has moved. Please update your links and bookmarks.</a>
- </body>
-</html>
-
diff --git a/faq/howto_banner.jpg b/faq/howto_banner.jpg
deleted file mode 100644
index f2e2d42..0000000
--- a/faq/howto_banner.jpg
+++ /dev/null
Binary files differ
diff --git a/faq/up_nav.gif b/faq/up_nav.gif
deleted file mode 100644
index 9b278e6..0000000
--- a/faq/up_nav.gif
+++ /dev/null
Binary files differ
diff --git a/freeze_plan_2_0.html b/freeze_plan_2_0.html
deleted file mode 100644
index 4b4dbfa..0000000
--- a/freeze_plan_2_0.html
+++ /dev/null
@@ -1,278 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<title>Eclipse Corner</title>
-<link rel="stylesheet" href="../default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=left width="80%">
- <p><font class=indextop>2.0 Freeze/Test/Fix<br>
- Master Schedule</font><br>
- <font class=indexsub> Updated frequently to reflect current status</font></p>
-</td>
- <td width="20%"><img SRC="../images/howto_banner.jpg" align=center width="272" height="111"></td>
- </tr>
-</table>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">Freeze
- Status</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td width="98%">
- <p>The eclipse team now in the 2.0 "lockdown" process which involves
- a sequence of freeze/test/fix passes. We welcome everyone to help us test
- and fix eclipse in these final stages before we finish 2.0. To participate,
- you need to track to the same schedule we do, test when we do, and get
- your <a href="http://dev.eclipse.org/bugs/">bugs</a> logged in time for
- them to be considered before the next freeze. It is critical that we all
- test at the same time. At each freeze the "bar" is raised on
- what is allowed to be changed, so windows of opportunity for fixing problems
- are narrow. It is virtually impossible to track exactly to a plan this
- detailed, so <i>we will update this schedule continuously to indicate
- current status, and what we are testing.</i> Be warned - this plan *will*
- change - check back frequently if you are participating with us. Bug reports
- to <a href="http://dev.eclipse.org/bugs/">bugzilla</a>. Process comments
- should be flagged on <a href="http://dev.eclipse.org/mailman/listinfo/eclipse-dev">eclipse-dev</a>.</p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td width="98%">
- <p><b><a href="testplans.html">Test Scenarios</a></b> - test scenarios to
- help drive testing.</p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td width="98%"><b><font color="#FF0000">June 28 Status</font></b>: Since
- version 1.0, eight months of hard work by the entire Eclipse community has
- culminated in the release of version 2.0 of Eclipse. It is ready for download
- <a href="http://download.eclipse.org/downloads" target="_top">here</a>. Without the support
- and enthusiasm of the entire Eclipse community we could not have achieved
- this. A big thank you to everyone in the newsgroups, on the mailings lists
- and especially everyone who reported bugs in Bugzilla.
- <p></p>
- </td>
- </tr>
-</table>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">How
- does it work?</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td width="98%">
- <p><b>Freeze</b> - Freeze time indicated is when the build starts. Target
- is to have freeze candidate build available within 24 hours of freeze.
- Getting a good, testable build may require multiple attempts in rapid
- succession. Although we may have a build, it will not be declared "the"
- freeze until the team validates the build and declares it good for testing.
- We will keep respinning the build until freeze can be declared. It is
- critical that we have enough time to do test passes. We will slide schedule
- and use weekends as necessary if there are delays of more than 24 hours
- in getting good freezes.</p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td width="98%">
- <p><b>Test</b> - After a freeze is declared, the full test pass begins on
- the freeze build. Each full test pass lasts 3 days. Each component team
- must have a test plan to ensure adequate coverage of function and platforms
- and to ensure everyone knows what to do. Each team is expected to have
- at least 75% of the team testing during every test pass. The rest of the
- team will be triaging bugs, preparing candidate fixes for critical problems
- coming in, or working on documentation. <i>Everyone is encouraged to participate
- in test passes and log bug reports to <a href="http://dev.eclipse.org/bugs/">bugzilla</a>!
- </i> If you uncover what you believe could be a serious or stop-ship problem,
- or a regression from a previous build, please make this very clear in
- the bug report. </p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top height="63" width="2%"><img src="../images/Adarrow.gif" border=0 width="16" height="16"></td>
- <td height="63" width="98%">
- <p><b>Fix</b> - At each successive freeze, the rules for what changes are
- allowed to the codebase, and what checks are required, become more restrictive.
- NOTE: The rules apply to both fixes and feature work - any changes to
- the code. All committers for a component have the right to veto a change
- (with an explanation) even after it has been released into the codebase.
- If such a veto occurs, the change automatically comes out unless the explanation
- is shown to be invalid or the vetoing committer's concerns are addressed.
- An Architecture Team member who approves work, or a Committer who checks
- a change and does not veto it, takes joint responsibility for the change
- with the Committer who releases it, and is implicitly agreeing to personally
- help fix any problem caused by the change. Any Committer for any Eclipse
- Project component can perform the checking duties.</p>
- </td>
- </tr>
-</table>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">Detailed
- Schedule </font></b></td>
- </tr>
-</table>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#FFFFFF">
- <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F1"></a>Tue
- May 21, 8:00am EST -- Freeze 1 (F1)</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">
- <p>Full Test pass:</p>
- </td>
- <td width="72%">Wed May 22, 8:00am EST - Fri May 24, 5:00pm EST</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Fix rule after F1:</td>
- <td width="72%">Component Lead must approve all work - no changes released
- without approval</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Notification requirements:</td>
- <td width="72%">N/A</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Check required on changes:</td>
- <td width="72%">N/A - However code check recommended at Component Lead discretion</td>
- </tr>
-</table>
-<hr>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#FFFFFF">
- <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F2"></a>Fri
- May 31, 8:00am EST -- Freeze 2 (F2)</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">
- <p>Full Test pass:</p>
- </td>
- <td width="72%">Mon Jun 3, 8:00am EST - Wed Jun 5, 5:00pm EST</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Fix rule after F2:</td>
- <td width="72%">Component Lead + 1 Arch Team member must approve all work
- - no changes released without approval</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Notification requirements:</td>
- <td width="72%">Intent to change must be announced to component mailing list</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Check required on changes:</td>
- <td width="72%">2nd Committer code check required, reporter verifies fix (where
- possible)</td>
- </tr>
-</table>
-<hr>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#FFFFFF">
- <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="F3"></a>Wed
- Jun 12, 8:00am EST -- Freeze 3 (F3)</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">
- <p>Verification Test pass:</p>
- </td>
- <td width="72%">Thu Jun 13, 8:00am EST - Mon Jun 17, 5:00pm EST</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Fix rule after F3:</td>
- <td width="72%">Architecture Team must approve all work</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Notification requirements:</td>
- <td width="72%">Intent to change must be announced to component mailing list</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Check required on changes:</td>
- <td width="72%">2nd and 3rd Committer code check required, reporter verifies
- fix (where possible)</td>
- </tr>
-</table>
-<hr>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#FFFFFF">
- <td align=left valign=top colspan="3"><b><font face="Arial,Helvetica" color="#000000"><a name="GM"></a>Monday
- Jun 24, 8:00am EST -- Golden Master Candidate (GM/F4) - Final code and doc</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">
- <p>Verification Test pass:</p>
- </td>
- <td width="72%">Tue Jun 25, 8:00am EST - Thu Jun 27, 5:00pm EST</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Fix rule after GM:</td>
- <td width="72%">NO CHANGES UNLESS A SERIOUS REGRESSION IS FOUND</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Notification requirements:</td>
- <td width="72%">Intent to change must be announced to component mailing list</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Check required on changes:</td>
- <td width="72%">2nd and 3rd Committer code check required, reporter verifies
- fix (where possible)</td>
- </tr>
-</table>
-<hr>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr bgcolor="#FFFFFF">
- <td align=left valign=top colspan="3"><b><font color="#000000"><b><font face="Arial,Helvetica" color="#000000"><a name="Release"></a></font><font face="Arial,Helvetica">Fri
- Jun 28, 8:00am EST</font></b></font> -- </b><font face="Arial,Helvetica" color="#000000"><b>Golden
- Master Release</b></font><font color="#000000"><b><font face="Arial,Helvetica">
- (R2.0) - Final code and doc</font></b></font></td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">
- <p>Verification Test pass:</p>
- </td>
- <td width="72%">N/A</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Fix rule after R2.0:</td>
- <td width="72%">NO CHANGES. FIXES AFTER THIS POINT ARE RELEASED WITH THE NEXT
- SERVICE UPDATE.</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Notification requirements:</td>
- <td width="72%">N/A</td>
- </tr>
- <tr>
- <td align=right valign=top width="3%"> </td>
- <td width="25%">Check required on changes:</td>
- <td width="72%">N/A</td>
- </tr>
-</table>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>.</p>
-</body>
-</html>
diff --git a/index.html b/index.html
deleted file mode 100644
index d0012f5..0000000
--- a/index.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<html>
- <head>
- <meta http-equiv="refresh" content="2; url=index.php" />
- </head>
- <body>
- <a href="index.php">This page has moved. Please update your links and bookmarks.</a>
- </body>
-</html>
\ No newline at end of file
diff --git a/main.html b/main.html
deleted file mode 100644
index d0012f5..0000000
--- a/main.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<html>
- <head>
- <meta http-equiv="refresh" content="2; url=index.php" />
- </head>
- <body>
- <a href="index.php">This page has moved. Please update your links and bookmarks.</a>
- </body>
-</html>
\ No newline at end of file
diff --git a/project-info/executive-summary.html b/project-info/executive-summary.html
deleted file mode 100644
index 175be19..0000000
--- a/project-info/executive-summary.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<p>The changes afoot for the 3.2 (Callisto) release of Eclipse
-Platform, JDT, PDE and Equinox will address major themes identified by
-the Eclipse Requirements Council (Themes and Priorities dated Dec. 15,
-2004 - <a href="http://www.eclipse.org/org/councils/20041215EclipseTPFinalDraft.pdf">pdf)</a>.
- The following are especially germane to this top level project:</p>
-<ul>
- <li><strong>Scaling Up</strong> - This refers to the need for Eclipse to deal
- with development and deployment on a larger and more complex scale. Increasing
- complexities arise from large development teams distributed in different locations,
- large source code bases and fragile build environments that have been developed
- incrementally over time, the dynamic nature of new source code bases and their
- interaction with configuration management, and build environments involving
- many different tools and build rules.</li>
- <li><strong>Enterprise Ready</strong> - Eclipse should be improved to allow
- it to be better used by large development organizations.</li>
-
- <li><strong>Design for Extensibility: Be a Better Platform</strong> - Within
- the Eclipse community, many development projects are defining new development
- platforms on top of the Eclipse Project deliverables. These must evolve
- to better support this type of usage, including providing new common infrastructure
- and abstraction layers needed by upper platforms and adding APIs to expose
- existing functionality only available internally so that upper platforms can
- more readily integrate with and reuse what's already there.</li>
- <li><strong>Simple to Use</strong> -
- The Eclipse components need to not only provide the features that advanced users demand,
- but also be something that most users find simple to use.</li>
- <li><strong>Rich Client Platform</strong> -
- The Eclipse RCP is a Java-based application framework for the desktop. Building on the
- Eclipse runtime and the modular plug-in story, it is possible to build applications ranging from
- command line tools to feature-rich applications that take full advantage of SWT's native
- platform integration and the many other reusable components.</li>
- <li><strong>Appealing to the Broader Community</strong> -
- This theme includes work that grows deeper roots into the various OS-specific communities,
- spreads Eclipse to additional operating environments, virtual machines, application
- development and deployment lifecycles, vertical market-specific frameworks and builds
- bridges to other open source communities.</li>
-</ul>
-
-The Eclipse project is continuing it progress towards these goals. Milestone 5 is on February 17th and is the API
-freeze. Development freeze occurs at M6/RC0 on March 31st. Following this is a period of
-rigorous testing and critical bug fixing. See the <a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html">full 3.2 plan</a>
-for more details.
\ No newline at end of file
diff --git a/project-info/home-page-one-liner.html b/project-info/home-page-one-liner.html
deleted file mode 100644
index 8ce5c58..0000000
--- a/project-info/home-page-one-liner.html
+++ /dev/null
@@ -1 +0,0 @@
-<a href="/eclipse/">Eclipse Project</a>
\ No newline at end of file
diff --git a/project-info/maillist b/project-info/maillist
deleted file mode 100644
index 9ad4e0e..0000000
--- a/project-info/maillist
+++ /dev/null
@@ -1,3 +0,0 @@
-::eclipse-dev::General development mailing list of the Eclipse Project.
-::eclipse-pmc::Discussion with the Eclipse Project Management Committee
-::e4-dev::General development mailing list of the e4 sub-project.
\ No newline at end of file
diff --git a/project-info/newsgroup b/project-info/newsgroup
deleted file mode 100644
index dcb3964..0000000
--- a/project-info/newsgroup
+++ /dev/null
@@ -1 +0,0 @@
-::eclipse.platform::Come here to participate in technical discussions about how to develop editors, views, preference pages, wizards, builders, etc for eclipse. If you think you've discovered a bug, or discovered a missing feature, you can ask a question here, or check the bug database. There may be another way of looking at the problem that fits better with the way eclipse works. Take a look here if you're having trouble figuring out how to get something to work. Ask your JFace questions here. And by all means please jump in and help others out by sharing your expertise and experience - the community only works if everyone contributes. And as with any newsgroup, keep in mind that the better the quality of the question, the better the quality of the answers you are likely to get!
\ No newline at end of file
diff --git a/project-info/project-info.xml b/project-info/project-info.xml
deleted file mode 100644
index bb445d1..0000000
--- a/project-info/project-info.xml
+++ /dev/null
@@ -1,101 +0,0 @@
-<project>
- <bugzilla>
- <product name="Equinox"/>
- <product name="JDT"/>
- <product name="PDE"/>
- <product name="Platform"/>
- </bugzilla>
- <committers url="/eclipse/commit.html"/>
- <contributors />
- <leaders url="/eclipse/team-leaders.html"/>
- <cvs repository="/cvsroot/eclipse/" />
- <description paragraph-url="/eclipse/project-info/project-page-paragraph.html"/>
- <summary paragraph-url="/eclipse/project-info/executive-summary.html"/>
- <getting-started url="http://www.eclipse.org/documentation/main.html"/>
- <ip-log />
- <mailing-lists>
- <list name="eclipse-dev"/>
- <list name="e4-dev"/>
- <list name="platform-dev"/>
- <list name="platform-ant-dev"/>
- <list name="platform-compare-dev"/>
- <list name="platform-core-dev"/>
- <list name="platform-cvs-dev"/>
- <list name="platform-debug-dev"/>
- <list name="platform-doc-dev"/>
- <list name="platform-help-dev"/>
- <list name="platform-releng-dev"/>
- <list name="platform-scripting-dev"/>
- <list name="platform-search-dev"/>
- <list name="platform-swt-dev"/>
- <list name="platform-team-dev"/>
- <list name="platform-text-dev"/>
- <list name="platform-ua-dev"/>
- <list name="platform-ui-dev"/>
- <list name="platform-update-dev"/>
- <list name="platform-webdav-dev"/>
- <list name="jdt-dev"/>
- <list name="jdt-apt-dev"/>
- <list name="jdt-core-dev"/>
- <list name="jdt-debug-dev"/>
- <list name="jdt-doc-dev"/>
- <list name="jdt-ui-dev"/>
- <list name="pde-dev"/>
- <list name="pde-build-dev"/>
- <list name="pde-doc-dev"/>
- <list name="pde-ui-dev"/>
- </mailing-lists>
- <newsgroups>
- <newsgroup name="eclipse.platform"/>
- <newsgroup name="eclipse.e4"/>
- <newsgroup name="eclipse.technology.equinox"/>
- <newsgroup name="eclipse.tools.jdt"/>
- <newsgroup name="eclipse.platform.rcp"/>
- <newsgroup name="eclipse.platform.swt"/>
- </newsgroups>
- <wiki url="http://wiki.eclipse.org/Eclipse"/>
- <project-plan url="/projects/project-plan.php?projectid=eclipse"/>
- <releases>
- <release name="3.1"
- date="6/2005"
- status="completed"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.1-200506271435/index.php"/>
- <release name="3.1.1"
- date="9/2005"
- status="completed"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.1.1-200509290840/index.php"/>
- <release name="3.1.2"
- date="1/2006"
- status="completed"/>
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.1.2-200601181600/index.php"/>
- <release name="3.2"
- date="29/6/2006"
- status="completed"
- plan="/eclipse/development/eclipse_project_plan_3_2.html"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/index.php"/>
- <release name="3.2.1"
- date="21/9/2006"
- status="completed"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/index.php"/>
- <release name="3.2.2"
- date="12/2/2007"
- status="completed"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.2.2-200702121330/index.php"/>
- <release name="3.3"
- date="25/6/2007"
- status="completed"
- plan="/eclipse/development/eclipse_project_plan_3_3.html"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500/index.php"/>
- <release name="3.3.1"
- date="9/2007"
- status="completed"
- download="http://download.eclipse.org/eclipse/downloads/drops/R-3.3.1-200709211145/index.php"/>
- <release name="3.3.2"
- date="2/2008"
- status="scheduled"/>
- <release name="3.4"
- date="6/2008"
- plan="/eclipse/development/eclipse_project_plan_3_4.html"
- status="scheduled"/>
- </releases>
-</project>
diff --git a/project-info/project-page-paragraph.html b/project-info/project-page-paragraph.html
deleted file mode 100644
index 92ab6a2..0000000
--- a/project-info/project-page-paragraph.html
+++ /dev/null
@@ -1,4 +0,0 @@
-<p><b><a href="/eclipse/">The Eclipse Top-Level Project</a></b>
-- an open source, robust, full-featured, commercial-quality, industry
-platform for the development of highly integrated tools
-and <a href="/rcp/">rich client applications</a></p>
\ No newline at end of file
diff --git a/team-leaders.html b/team-leaders.html
deleted file mode 100644
index e5478ff..0000000
--- a/team-leaders.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<html>
- <head>
- <meta http-equiv="refresh" content="2; url=team-leaders.php" />
- </head>
- <body>
- <a href="index.php">This page has moved. Please update your links and bookmarks.</a>
- </body>
-</html>
\ No newline at end of file
diff --git a/testplans.html b/testplans.html
deleted file mode 100644
index 451922b..0000000
--- a/testplans.html
+++ /dev/null
@@ -1,176 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<title>Eclipse Corner</title>
-<link rel="stylesheet" href="../default_style.css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
-<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
- <tr>
- <td ALIGN=left width="80%">
- <p><font class=indextop>Eclipse Project</font><font class=indextop><br>
- 2.0 Test Scenarios</font><br>
- <font class=indexsub> Supplementary Test information for 2.0</font></p>
- </td>
- <td width="20%"><img SRC="../images/howto_banner.jpg" height=111 width=272 align=center></td>
- </tr>
-</table>
-<table border=0 cellspacing=5 cellpadding=2 width="100%" >
- <tr>
- <td align=left valign=top colspan="4" bgcolor="#0080c0"><b><font face="Arial,Helvetica" color="#ffffff">Test
- Scenarios</font></b></td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"> </td>
- <td colspan="3">
- <p>In addition to the automated tests that run on each build, some of the
- teams have specific test plans and scenarios to help drive testing. This
- section provides links to the test scenarios and plans the Eclipse Project
- component teams are using to help drive testing during the 2.0 freeze/test/fix
- passes. You can use these to follow along, or to help guide your own testing.
- We'll post more of them as they become available.<br>
- <br>
- NOTE: If you are participating in the test/freeze cycle please subscribe
- to <a href="http://dev.eclipse.org/mailman/listinfo/eclipse-dev">eclipse-dev</a>
- - all major build/freeze/test announcements will be made to this list.
- Please use bugzilla for all bug reports.</p>
- </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"> </td>
- <td width="34%">
- <p><b>Plan Document</b></p>
- </td>
- <td width="31%">
- <div align="right"><b>Developer Mailing List</b></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.jdt.debug.tests/testplans/Debug%20Test%20Plan%202.0.htm?rev=HEAD&content-type=text/html">Debug
- Test Plan</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-debug-dev">platform-debug-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-debug-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-help-home/testing/scenarios.html">Help
- System Test Scenarios</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-help-dev">platform-help-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-help-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%" height="19"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%" height="19">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/testpass1.htm">JDT-UI,
- Editor, Search, Compare Test Plan</a></b></p>
- </td>
- <td width="31%" height="19">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev">jdt-ui-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/jdt-ui-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%" height="19"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b>JDT Core / Post Freeze 1 : <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r2.0/test-pass-1.html">Testing
- Plan,</a> <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r2.0/fix-pass-1.html">Fix
- Plan</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/jdt-core-dev">jdt-core-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/jdt-core-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/pde-ui-home/scenarios/PDEScenarios.html">PDE
- Usage Scenarios</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/pde-ui-dev">pde-ui-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/pde-ui-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/testplan.html">Platform
- Core Tests</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-core-dev">platform-core-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-core-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/SWT_R2_0_Test_Plan.html">SWT
- Test Plan</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-swt-dev">platform-swt-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-swt-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/2_0_testing.html">Team/CVS
- Test Plan</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev">platform-vcm-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-vcm-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/testfix/TestPass2.html">Workbench
- (org.eclipse.ui) Test Plan for Test Pass 2</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-ui-dev">platform-ui-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-ui-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
- <tr>
- <td align=right valign=top width="4%"><img src="../images/Adarrow.gif" border=0 height=16 width=16></td>
- <td width="34%">
- <p><b><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/doc/Test%20Scenarios/eclipse%20update.html">Update/Install
- Test Scenarios</a></b></p>
- </td>
- <td width="31%">
- <div align="right"><a href="http://dev.eclipse.org/mailman/listinfo/platform-update-dev">platform-update-dev</a>
-   <a href="http://dev.eclipse.org/mhonarc/lists/platform-update-dev/maillist.html">archive</a></div>
- </td>
- <td width="31%"> </td>
- </tr>
-</table>
-<p>Please see our <a href="http://www.eclipse.org/legal/privacy.html">privacy
- policy</a> and website <a href="http://www.eclipse.org/legal/termsofuse.html">terms
- of use</a>.</p>
-</body>
-</html>
