Attachment 66939 Details for Bug 185753 – Updates for all sections except "known issues"

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Updates for all sections except "known issues"

patch.txt (text/plain), 45.74 KB, created by John Arthorne

on 2007-05-11 16:46:55 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: John Arthorne

Created: 2007-05-11 16:46:55 EDT

Size: 45.74 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.platform-feature
>Index: rootfiles/readme/readme_eclipse.html
>===================================================================
>RCS file: /cvsroot/eclipse/org.eclipse.platform-feature/rootfiles/readme/readme_eclipse.html,v
>retrieving revision 1.82
>diff -u -r1.82 readme_eclipse.html
>--- rootfiles/readme/readme_eclipse.html	10 May 2007 17:23:34 -0000	1.82
>+++ rootfiles/readme/readme_eclipse.html	11 May 2007 20:45:55 -0000
>@@ -3,7 +3,7 @@
> 
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
>-<title>Eclipse Project Release Notes 3.2</title>
>+<title>Eclipse Project Release Notes 3.3</title>
> </head>
> 
> <body>
>@@ -30,7 +30,6 @@
> <p>In order to remain current, each Eclipse release targets reasonably current
>   operating environments.
> </p>
>-
> <p>Most of the Eclipse SDK is "pure" Java code and has no direct
>   dependence on the underlying operating system. The chief dependence is
>   therefore on the Java Platform itself. Portions of the Eclipse SDK
>@@ -38,17 +37,15 @@
>   to specific classes of operating environments, requiring their source
>   code to only reference facilities available in particular class
>   libraries (e.g. J2ME Foundation 1.0, J2SE 1.3 and 1.4, etc.).
>-</p>
>-<p>  
>-  With the exception of a small set of features that
>-  actually require Java SE 5 APIs (in particular, the support for
>-  Annotation Processing and JUnit 4), the 3.2 release of the Eclipse
>-  Project runs against version 1.4 of the Java 2 Platform.
>-  As such, the Eclipse Project SDK as a whole is targeted at both
>-  1.4 and Java5 VMs, with full functionality available for 1.4 level
>-  development everywhere, and new Java5 specific capabilities available
>-  when running on a Java5 VM.
>-
>+ </p><p> 
>+  In general, the 3.3 release of the Eclipse Project is developed on a
>+  mix of Java 1.4 and Java5 VMs. As such, the Eclipse Project SDK as
>+  a whole is targeted at both 1.4 and Java5 VMs, with full functionality 
>+  available for 1.4 level development everywhere, and new Java5 specific
>+  capabilities available when running on a Java5 VM. Similarly, in cases
>+  where support has been added for Java6 specific features (e.g. JSR-199,
>+  JSR-269, etc.) Java6 VMs are required.
>+</p><p>
>   <a href="#Appendix1">Appendix 1</a> contains a table that indicates
>   the class library level required for each plug-in.
> </p>
>@@ -57,337 +54,248 @@
>   a variety of operating systems. We focus Eclipse SDK testing on a handful 
>   of popular combinations of operating system and Java Platform; 
>   these are our <em>reference platforms</em>. Eclipse undoubtedly runs fine in 
>-  many operating environments beyond the reference platforms we test. However, 
>-  since we do not systematically test them we cannot vouch for them. Problems 
>-  encountered when running Eclipse on a non-reference platform that cannot be recreated 
>-  on any reference platform are given lower priority than problems with running 
>-  Eclipse on a reference platform.</p>
>-<p>The Eclipse SDK 3.2 is tested and validated on the following reference platforms:</p>
>-
>-<table summary="Eclipse Reference Platforms" style="width: 821px;" border="1">
>-  <tbody>
>-    <tr bgcolor="#cccccc">
>-      <th colspan="5">
>-        <div align="center"><strong><font size="+1">Eclipse Reference Platforms</font></strong></div>
>-      </th>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205"><b>Operating system</b></td>
>-      <td width="59"><b>OS version</b></td>
>-
>-      <td width="76"><b>Processor architecture</b></td>
>-      <td width="59"><b>Window system</b></td>
>-      <td width="453"><b>Java 2 Platform</b></td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Microsoft Windows</td>
>-      <td width="59">XP</td>
>-
>-      <td width="76">Intel x86</td>
>-      <td width="59">Win32</td>
>-      <td width="453">
>-        Sun Java 2 Standard Edition 5.0 Update 6<br>for Microsoft Windows
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Microsoft Windows</td>
>-
>-      <td width="59">XP</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">Win32</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Windows,<br>Java 2 Technology Edition 5.0 service release 1
>-      </td>
>-    </tr>
>-
>-    
>-    <tr>
>-      <td width="205">Microsoft Windows</td>
>-      <td width="59">XP</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">Win32</td>
>-      <td width="453"> 
>-        Sun Java 2 Standard Edition 1.4.2_10<br>for Microsoft Windows
>-      </td>
>-
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Microsoft Windows</td>
>-      <td width="59">XP</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">Win32</td>
>-      <td width="453">
>-
>-        IBM 32-bit SDK for Windows,<br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Red Hat Enterprise Linux</td>
>-      <td width="59">WS 4</td>
>-      <td width="76">Intel x86</td>
>-
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on Intel architecture,<br>Java 2 Technology Edition 5.0 service release 1
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Red Hat Enterprise Linux</td>
>-      <td width="59">WS 4</td>
>-
>-      <td width="76">Intel x86</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        Sun Java 2 Standard Edition 1.4.2_10<br>for Linux x86
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Red Hat Enterprise Linux</td>
>-
>-      <td width="59">WS 4</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on Intel architecture,<br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>-    </tr>
>-
>-    
>-    <tr>
>-      <td width="205">Red Hat Enterprise Linux</td>
>-      <td width="59">WS 4</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        Sun Java 2 Standard Edition 5.0 Update 6<br> for Linux x86</td>
>-
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">SUSE Linux Enterprise Server</td>
>-      <td width="59">9</td>
>-      <td width="76">Intel x86</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>+  many operating environments beyond the reference platforms we test, including
>+  those using Java6 VMs. However, since we do not systematically test them we
>+  cannot vouch for them. Problems encountered when running Eclipse on a non-reference
>+  platform that cannot be recreated on any reference platform will be given lower
>+  priority than problems with running Eclipse on a reference platform.</p>
>+  
>+<p>
>+The Eclipse SDK 3.3 is tested and validated on the following reference platforms:</p>
> 
>-        Sun Java 2 Standard Edition 1.4.2_10<br>for Linux x86</td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">SUSE Linux Enterprise Server</td>
>-      <td width="59">9</td>
>-      <td width="76">Intel x86</td>
>+<center>
>+<table border="1" cellpadding="2" cellspacing="2" width="80%" summary="Eclipse Reference Platforms">
>+<tbody>
>+
>+<tr align="center">
>+<td><b>Reference Platforms</b></td>
>+</tr>
> 
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on Intel architecture,<br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Sun Solaris</td>
>-      <td width="59">10</td>
>+<tr><td>
>+<b>Microsoft Windows Vista, x86-32, Win32</b> running (any of):
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Microsoft Windows</li>
>+<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR4 (see caveat below)</li>
>+<li>BEA JRockit 5.0, for Microsoft Windows</li>
>+</ul>
>+</td></tr>
> 
>-      <td width="76">SPARC</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        Sun Java 2 Standard Edition 1.4.2_10<br>for Solaris SPARC</td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">HP HP-UX</td>
>+<tr><td>
>+<b>Microsoft Windows XP, x86-32, Win32</b> running (any of):
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Microsoft Windows</li>
>+<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR4</li>
>+<li>BEA JRockit 5.0, for Microsoft Windows</li>
>+<li>Sun Java 2 Standard Edition 1.4.2_14 for Microsoft Windows</li>
>+<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 1.4.2 SR7</li>
>+<li>BEA JRockit 1.4.2, for Microsoft Windows</li>
>+</ul>
>+</td></tr>
> 
>-      <td width="59">11i</td>
>-      <td width="76">hp9000<br>PA-RISC</td>
>-      <td width="59">Motif</td>
>-      <td width="453">
>-        HP-UX JDK for the Java 2 Platform Standard Edition for 1.4.2_09
>-      </td>
>-    </tr>
>+<tr><td>
>+<b>Red Hat Enterprise Linux 4.0 update 2, x86-32, GTK</b> running (any of):
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86</li>
>+<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR4</li>
>+<li>BEA JRockit 5.0, for Linux x86</li>
>+<li>Sun Java 2 Standard Edition 1.4.2_13 for Linux x86</li>
>+<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 1.4.2 SR7</li>
>+<li>BEA JRockit 1.4.2, for Linux x86</li>
>+</ul>
>+</td></tr>
> 
>-    
>-    <tr>
>-      <td width="205">IBM AIX 5L</td>
>-      <td width="59">5.2</td>
>-      <td width="76">Power</td>
>-      <td width="59">Motif</td>
>-      <td width="453">
>-        IBM 32-bit SDK for AIX,<br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>+<tr><td>
>+<b>SUSE Linux Enterprise Server 10, x86-32, GTK</b> running (any of):
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86</li>
>+<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR4</li>
>+</ul>
>+</td></tr>
> 
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Apple Mac OS X</td>
>-      <td width="59">10.4</td>
>-      <td width="76">Power, Intel x86</td>
>-      <td width="59">Carbon</td>
>-      <td width="453">
>+<tr><td>
>+<b>Red Hat Enterprise Linux 4.0 update 2, x86-64, GTK</b> running:
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86_64</li>
>+</ul>
>+</td></tr>
> 
>-        Java 2 Platform Standard Edition (J2SE) 1.4.2<br>service release 2 for Tiger
>-      </td>
>-    </tr>
>-    
>-    <tr>
>-      <td width="205">Red Hat Enterprise Linux</td>
>-      <td width="59">WS 4</td>
>-      <td width="76">Power</td>
>+<tr><td>
>+<b>Sun Solaris 10, SPARC, GTK</b> running:
>+<ul>
>+<li>Sun Java 2 Standard Edition 5.0 Update 11 for Solaris SPARC</li>
>+</ul>
>+</td></tr>
> 
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on pSeries architecture, <br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>-    </tr>
>+<tr><td>
>+<b>IBM AIX 5.3, Power, Motif 2.1</b> running:
>+<ul>
>+<li>IBM 32-bit SDK, Java 2 Technology Edition 5.0, SR4</li>
>+</ul>
>+</td></tr>
> 
>-    <tr>
>-      <td width="205">SUSE Linux Enterprise Server</td>
>+<tr><td>
>+<b>Red Hat Enterprise Linux 4.0 update 2, Power, GTK</b> running:
>+<ul>
>+<li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 1.4.2 service release 7</li>
>+</ul>
>+</td></tr>
> 
>-      <td width="59">9</td>
>-      <td width="76">Power</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on pSeries architecture, <br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>-    </tr>
>+<tr><td>
>+<b>SUSE Linux Enterprise Server 10, Power, GTK</b> running:
>+<ul>
>+<li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 1.4.2 service release 7</li>
>+</ul>
>+</td></tr>
> 
>-    
>-    <tr>
>-      <td width="205">SUSE Linux Enterprise Server</td>
>-      <td width="59">9</td>
>-      <td width="76">Power</td>
>-      <td width="59">GTK</td>
>-      <td width="453">
>-        IBM 32-bit SDK for Linux on pSeries architecture, <br>Java 2 Technology Edition 1.4.2 service release 3
>-      </td>
>+<tr><td>
>+<b>Apple Mac OS X 10.4, Universal, Carbon</b> running:
>+<ul>
>+<li>Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4 for Tiger</li>
>+</ul>
>+</td></tr>
> 
>-    </tr>
>-    
>-  </tbody>
>+</tbody>
> </table>
>+</center>
> 
>-<p>Because Java 1.4.2 platforms are used for most Eclipse development,
>-  in general, 1.4.2 platforms are listed here. Of course, the teams doing Java 5 based
>-  development use Java 5 platforms, and the specific ones that they test on
>-  are also included. <i>We expect that Eclipse works fine on other Java 5 VMs
>+<dl>
>+<dt><em>Caveat: Using IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR4 on Vista</em></dt>
>+<dd>Although we expect this to be fixed in IBM Java5 SR5, there is currently a conflict between
>+the use of DirectDraw by the <strong>AWT</strong> libraries in IBM Java5 SR4 and
>+the Windows Vista "Aero" theme. Although the Eclipse SDK itself does not use these libraries
>+(and thus runs well on Windows Vista using that VM), other plug-ins that make use of the 
>+conflicting AWT capabilities may cause the advanced features of Aero to be disabled. As a
>+workaround to avoid this problem, you can add <code>-Dsun.java2d.noddraw=true</code> to the
>+VM arguments when launching Eclipse, which will prevent the AWT libraries from using DirectDraw. 
>+</dd>
>+</dl>
>+
>+<p>Because Java 1.4.2 and Java5 based platforms are used for most Eclipse
>+  development, those platforms are listed here. Although there are teams
>+  doing some Java 6 based development we have not included specific Java6 VMs,
>+  since they have not yet received the general level of testing we require.
>+  <i>We expect that Eclipse will work fine on other current Java VMs
>   running on window systems supported by SWT, but can not flag these as reference
>   platforms without significant community support for testing them.</i></p>
>   
> <p>Similarly, although untested, the Eclipse SDK should work fine on other OSes that 
>-  support the same window system. For Win32: Windows 98, ME, NT, 2000, and Server 
>+  support the same window system. For Win32: NT, 2000, and Server 
>   2003; SWT HTML viewer requires Internet Explorer 5 (or higher). For GTK on other 
>   Linux systems: version 2.2.1 of the GTK+ widget toolkit and associated libraries 
>   (GLib, Pango); SWT HTML viewer requires Mozilla 1.4GTK2. For Motif on 
>   Linux systems: Open Motif 2.1 (included); SWT HTML viewer requires Mozilla 1.4GTK2.</p>
> 
>-<p>An early access version of the Eclipse SDK is also available for 64-bit 
>-  Linux GTK. Testing has been limited to early access 64-bit J2SEs running on 
>-  x86-64 processors.</p>
>-  
> <p>SWT is also supported on the QNX Neutrino operating system, x86 processor, 
>-  Photon window system, and IBM J9 VM version 2.0. Eclipse 3.2 on Windows or Linux 
>-  can be used to cross-develop QNX applications. (Eclipse 3.2 is unavailable on QNX 
>-  because there is currently no 1.4 J2SE for QNX.)</p>
>-
>-  <p></p>
>+  Photon window system, and IBM J9 VM version 2.0. Eclipse 3.3 on Windows or Linux 
>+  can be used to cross-develop QNX applications. (Eclipse 3.3 is unavailable on QNX 
>+  because there is currently no 1.5 J2SE for QNX.)</p>
>+<p></p>
> <p> </p>
> <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 are supported by the Eclipse SDK on all of the above
>-operating environments; DBCS locales are supported by the Eclipse SDK on the
>-Windows, GTK, and Motif window systems; BIDI locales are supported by the
>-Eclipse SDK only on Windows operating environments.
>-<p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, 
>-  on Windows XP and 2000, and Linux. 
>+
>+<p>The Eclipse SDK 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 are supported by the Eclipse SDK on all of the above 
>+  operating environments; DBCS locales are supported by the Eclipse SDK 
>+  on the Windows, GTK, and Motif window systems; BIDI locales are supported by 
>+  the Eclipse SDK only on Windows operating environments.</p>
>+
>+<p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page 
>+  standard, on Windows XP and 2000, and Linux/GTK.</p>
>+
> <p>German and Japanese locales are tested.</p>
> 
> <h4>BIDI support</h4>
>-<p>SWT fully supports BIDI on Windows only. On Linux GTK, SWT supports entering 
>-  and displaying BIDI text.</p>
>-<p>The Eclipse SDK is a development environment targeted at technical professionals 
>-  - not an end user application. However, the Eclipse SDK 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 allows a Java programmer to work with BIDI strings, code 
>-  comments, etc. On the Windows platform only, the Eclipse SDK itself can be 
>-  localized for BIDI locales and the widget orientation will change appropriately.
>-</p>
> 
>-<h2>2. <a name="Compatibility"></a>Compatibility with Previous Releases</h2>
>+<p>SWT fully supports BIDI on Windows. On Linux GTK, SWT supports entering 
>+  and displaying BIDI text. Within these limitations, the Eclipse
>+  SDK tools are BIDI enabled.</p>
> 
>+<h2>2. <a name="Compatibility"></a>Compatibility with Previous Releases</h2>
> 
>-<h3>Compatibility of Release 3.2 with 3.1</h3>
>+<h3>Compatibility of Release 3.3 with 3.2</h3>
> 
>-<p>Eclipse 3.2 is compatible with Eclipse 3.1 (and, hence, with 3.0).</p>
>-<p><b>API Contract Compatibility:</b> Eclipse SDK 3.2 is upwards contract-compatible 
>-  with Eclipse SDK 3.1 except in those areas noted in the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html" target="_top"><em>Eclipse 
>-  3.2 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension 
>-  points will need to be ported to Eclipse SDK 3.2 APIs. Downward contract compatibility 
>-  is not supported. There is no guarantee that compliance with Eclipse SDK 3.2 
>-  APIs would ensure compliance with Eclipse SDK 3.1 APIs. Refer to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving 
>-  Java-based APIs</a></i> for a discussion of the kinds of API changes that maintain 
>-  contract compatibility.</p>
>-
>-<p><b>Binary (plug-in) Compatibility:</b> Eclipse SDK 3.2 is upwards binary-compatible 
>-  with Eclipse SDK 3.1 except in those areas noted in the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html" target="_top"><em>Eclipse 
>-  3.2 Plug-in Migration Guide</em></a>. Downward plug-in compatibility is not 
>-  supported. Plug-ins for Eclipse SDK 3.2  are not usable in Eclipse SDK 3.1. 
>-  Refer to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving 
>-  Java-based APIs</a></i> for a discussion of the kinds of API changes that maintain 
>-  binary compatibility. 
>-</p><p><b>Source Compatibility:</b> Eclipse SDK 3.2 is upwards source-compatible 
>-  with Eclipse SDK 3.1 except in the areas noted in the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html" target="_top"><em>Eclipse 
>-  3.2 Plug-in Migration Guide</em></a>. This means that source files written to 
>-  use Eclipse SDK 3.1 APIs might successfully compile and run against Eclipse 
>-  SDK 3.2 APIs, although this is not guaranteed. Downward source compatibility 
>+<p>Eclipse 3.3 is compatible with Eclipse 3.2.</p>
>+<p>
>+  <strong>API Contract Compatibility:</strong> Eclipse SDK 3.3 is upwards contract-compatible 
>+  with Eclipse SDK 3.2 except in those areas noted in the 
>+  <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html" target="_top">
>+    <em>Eclipse 3.3 Plug-in Migration Guide</em>
>+  </a>. 
>+  Programs that use affected APIs and extension points will need to be ported to
>+  Eclipse SDK 3.3 APIs. Downward contract compatibility is not supported.
>+  There is no guarantee that compliance with Eclipse SDK 3.3 
>+  APIs would ensure compliance with Eclipse SDK 3.2 APIs. Refer to 
>+  <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
>+    <em>Evolving Java-based APIs</em>
>+  </a> for a discussion of the kinds of API changes that maintain contract compatibility.
>+</p>
>+<p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 3.3 is upwards binary-compatible 
>+  with Eclipse SDK 3.2 except in those areas noted in the
>+  <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html" target="_top">
>+    <em>Eclipse 3.3 Plug-in Migration Guide</em>
>+  </a>. 
>+  Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.3
>+  will not be usable in Eclipse SDK 3.2. Refer to
>+  <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
>+    <em>Evolving Java-based APIs</em>
>+    </a> for a discussion of the kinds of API changes that maintain binary compatibility. 
>+</p>
>+<p><strong>Source Compatibility:</strong> Eclipse SDK 3.3 is upwards source-compatible 
>+  with Eclipse SDK 3.2 except in the areas noted in the 
>+  <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html" target="_top">
>+    <em>Eclipse 3.3 Plug-in Migration Guide</em>
>+  </a>. 
>+  This means that source files written to 
>+  use Eclipse SDK 3.2 APIs might successfully compile and run against Eclipse 
>+  SDK 3.3 APIs, although this is not guaranteed. 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><p><b>Workspace Compatibility:</b> Eclipse SDK 3.2 is upwards workspace-compatible 
>-  with Eclipse SDK 3.1 unless noted. This means that workspaces and projects created 
>-  with Eclipse SDK 3.1 or 3.0 can be successfully opened by Eclipse SDK 3.2 and 
>-  upgraded to a 3.2 workspace. This includes both hidden metadata, which is localized 
>+</p>
>+<p><strong>Workspace Compatibility:</strong> Eclipse SDK 3.3 is upwards workspace-compatible 
>+  with Eclipse SDK 3.2 unless noted. This means that workspaces and projects created 
>+  with Eclipse SDK 3.2, 3.1 or 3.0 can be successfully opened by Eclipse SDK 3.3 and 
>+  upgraded to a 3.3 workspace. This includes both hidden metadata, which is localized 
>   to a particular workspace, as well as metadata files found within a workspace 
>   project (e.g., the .project file), which may propagate between workspaces via 
>   file copying or team repositories. Individual plug-ins developed for Eclipse 
>-  SDK 3.2 should provide similar upwards compatibility for their hidden and visible 
>-  workspace metadata created by earlier versions; 3.2 plug-in developers are responsible 
>-  for ensuring that their plug-ins recognize 3.1, 3.0, 2.1, and 2.0 metadata and 
>+  SDK 3.3 should provide similar upwards compatibility for their hidden and visible 
>+  workspace metadata created by earlier versions; 3.3 plug-in developers are responsible 
>+  for ensuring that their plug-ins recognize 3.2, 3.1, 3.0, 2.1, and 2.0 metadata and 
>   process it appropriately. User interface session state may be discarded when 
>   a workspace is upgraded. Downward workspace compatibility is not supported. 
>-  A workspace created (or opened) by a product based on Eclipse 3.2 is unusable 
>+  A workspace created (or opened) by a product based on Eclipse 3.3 will be unusable 
>   with a product based an earlier version of Eclipse. Visible metadata files created 
>-  (or overwritten) by Eclipse 3.2 will generally be unusable with earlier versions 
>+  (or overwritten) by Eclipse 3.3 will generally be unusable with earlier versions 
>   of Eclipse. 
>-</p><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 earlier releases. 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.
> </p>
>-
>-<h3>Compatibility of Release 3.2 with 3.0, 2.1 and 2.0</h3>
>-<p>Since Eclipse 3.1 is compatible with Eclipse 3.0, 2.1 and 2.0 in most regards, and 
>-  Eclipse 3.2 is compatible with 3.1, it follows that 3.2 is also compatible with 
>-  3.0, 2.1 and 2.0 in most aspects. If you are upgrading directly from 3.0, 2.1 or 2.0, 
>+<p><strong>Non-compliant usage of API's</strong>: 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 earlier releases. Refer to
>+  <a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">
>+    <em>How to Use the Eclipse API</em>
>+  </a> for information about how to write compliant plug-ins.
>+</p>
>+
>+<h3>Compatibility of Release 3.3 with 3.2, 3.1, 3.0, 2.1 and 2.0</h3>
>+<p>Since Eclipse 3.3 is compatible with Eclipse 3.2, 3.1, 3.0, 2.1 and 2.0 in most regards, and 
>+  Eclipse 3.3 is compatible with 3.2, it follows that 3.3 is also compatible with 
>+  3.2, 3.1, 3.0, 2.1 and 2.0 in most aspects. If you are upgrading directly from 3.1, 3.0, 2.1 or 2.0, 
>   refer also to the 
>-  <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html" target="_top">
>-  <em>Eclipse 3.0 Plug-in Migration Guide</em></a> 
>-  and the 
>   <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_1_porting_guide.html" target="_top">
>-  <em>Eclipse 3.1 Plug-in Migration Guide</em></a> for problems areas.</p>
>+  <em>Eclipse 3.1 Plug-in Migration Guide</em></a> 
>+  and the 
>+  <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_2_porting_guide.html" target="_top">
>+  <em>Eclipse 3.2 Plug-in Migration Guide</em></a> for problems areas.</p>
>+
>+
> <h2>3. <a name="Known Issues"></a> Known Issues</h2>
> <blockquote>
>   <p><a href="#I-Platform">3.1 Platform</a><br>
>@@ -418,7 +326,7 @@
> <h4>Installation/Configuration issues that can cause Eclipse to fail start</h4>
> <p>Here are some common problems that can cause Eclipse not to start:</p>
> <ul>
>-  <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 3.2 requires 
>+  <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 3.3 requires 
>     at least a 1.4.2 VM. Perhaps an older version of the VM is being found in 
>     your path. To explicitly specify which VM to run with, use the Eclipse <tt>-vm</tt> 
>     command-line argument. (See also the <a href="#Running Eclipse">Running Eclipse</a> 
>@@ -1430,8 +1338,8 @@
> 
> <h2>6. <a name="Interoperability with Previous Releases">Interoperability with
> Previous Releases</a></h2>
>-<h3>6.1 Interoperability of Release 3.2 and 3.1</h3>
>-<h4>Sharing projects between heterogeneous Eclipse 3.2 and 3.1</h4>
>+<h3>6.1 Interoperability of Release 3.3 with previous releases</h3>
>+<h4>Sharing projects between heterogeneous Eclipse 3.3 and 3.2</h4>
> <p>Special care is required when a project in a team repository is being loaded
> and operated on by developers using Eclipse-based products based on different
> feature or plug-in versions. The general problem is that the existence,
>@@ -1439,51 +1347,51 @@
> to a particular feature or plug-in version, and differ between versions. The
> workspace compatibility guarantees only cover cases where all developers upgrade
> their Eclipse workspaces in lock step. In those cases there should be no problem
>-with shared metadata. However, when some developers are working in Eclipse 3.2
>-while others are working in Eclipse 3.1, there are no such guarantees.
>-This section provides advice for what to do and to not do. It addresses the
>+with shared metadata. However, when some developers are working in Eclipse 3.3
>+while others are working in Eclipse 3.2, there are no such guarantees.
>+This section provides advice for what to do and not to do. It addresses the
> specific issues with the Eclipse SDK.</p>
> 
>-<p>The typical failure mode is noticed by the 3.2 user. 3.2 metadata is lost
>-when a 3.1 user saves changes and then commits the updated metadata files to the
>+<p>The typical failure mode is noticed by the 3.3 user. 3.3 metadata is lost
>+when a 3.2 user saves changes and then commits the updated metadata files to the
> repository. Here's how things typically go awry:</p>
> <ul>
>-  <li>A user working in Eclipse 3.2 creates or modifies a project in a way that
>-    results in changes to a shared metadata file that rely on 3.2-specific
>+  <li>A user working in Eclipse 3.3 creates or modifies a project in a way that
>+    results in changes to a shared metadata file that rely on 3.3-specific
>     information. The user then commits the updated project files, including the
>     shared metadata file, to the shared repository.</li>
>-  <li>Another user working in Eclipse 3.1 shares this project from the same
>-    repository. The 3.2-specific information in the shared metadata file is not
>-    understood by Eclipse 3.1, and is generally discarded or ignored without
>+  <li>Another user working in Eclipse 3.2 shares this project from the same
>+    repository. The 3.3-specific information in the shared metadata file is not
>+    understood by Eclipse 3.2, and is generally discarded or ignored without
>     warning. The user modifies the project in a way that results in changes to
>     the shared metadata file, causing the shared metadata file to be rewritten
>-    without any of the 3.2-specific information. The user commits the updated
>+    without any of the 3.3-specific information. The user commits the updated
>     project files, including the shared metadata file, to the shared repository.
>     The user is generally unaware that shared information has just been lost as
>     a result of their actions.</li>
>-  <li>A user working in Eclipse 3.2 picks up the changes to a project from the
>+  <li>A user working in Eclipse 3.3 picks up the changes to a project from the
>     shared repository, including the updated shared metadata file. The user may
>     be unaware that they have just taken a retrograde step until later when
>     things start to malfunction.</li>
> </ul>
> <p>Here are some things to watch out for when sharing projects between
>-Eclipse 3.2 and 3.1:</p>
>+Eclipse 3.3 and 3.1:</p>
> <ul>
>   <li><b>Linked resources in the .project file</b><br>
>-  Eclipse 3.2 supports creating linked resources at arbitrary depth within a project,
>+  Eclipse 3.3 supports creating linked resources at arbitrary depth within a project,
>   and supports creating linked resources referring to other file systems. Neither of
>   these scenarios are supported in Eclipse 3.1 or earlier.  If such linked resources
>-  are created in 3.2, and the project is subsequently loaded into an Eclipse 3.1
>+  are created in 3.3, and the project is subsequently loaded into an Eclipse 3.1
>   or earlier workspace, these links will not be recognized.  Recommendation:
>   avoid creating links at arbitrary depth or to other file systems where project
>   compatibility with Eclipse 3.1 or earlier is required.</li>
> </ul>
>-<h4>Using Eclipse 3.2 to develop plug-ins that work in Eclipse 3.1</h4>
>-<p>It is also possible (and reasonable) to use Eclipse 3.2 to develop a plug-in 
>-  intended to work in Eclipse 3.1 or earlier. Use the <b>Plug-in Development &gt; 
>+<h4>Using Eclipse 3.3 to develop plug-ins that work in Eclipse 3.2</h4>
>+<p>It is also possible (and reasonable) to use Eclipse 3.3 to develop a plug-in 
>+  intended to work in Eclipse 3.2 or earlier. Use the <b>Plug-in Development &gt; 
>   Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse 
>-  3.1 install. This ensures that the code for your plug-in is being compiled and 
>-  tested against Eclipse 3.1 APIs, extension points, and plug-ins. (The above 
>+  3.2 install. This ensures that the code for your plug-in is being compiled and 
>+  tested against Eclipse 3.2 APIs, extension points, and plug-ins. (The above 
>   list of concerns do not apply since they affect the layout and interpretation 
>   of files in the plug-in <i>project</i> but none affect the actual deployed form 
>   of the plug-in.)</p>
>@@ -1493,7 +1401,7 @@
> in the United States, other countries, or both.</p>
> <p>IBM is a trademark of International Business Machines Corporation in the
> United States, other countries, or both.</p>
>-<p>Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
>+<p>Microsoft, Windows, Windows NT, Vista, and the Windows logo are trademarks of
> Microsoft Corporation in the United States, other countries, or both.</p>
> <p>Apple and Mac OS are trademarks of Apple Computer, Inc., registered in the
> U.S. and other countries.</p>
>@@ -1501,21 +1409,22 @@
> Software Systems Ltd.</p>
> <p>Other company, product, and service names may be trademarks or service marks
> of others.</p>
>-<p>(c) Copyright IBM Corp. and others 2006</p>
>+<p>(c) Copyright IBM Corp. and others 2007</p>
> 
> <h2><a name="Appendix1">Appendix 1: Execution Environment by Plug-in</a></h2>
> 
>-<p>In the table below, the "3.2 EE" ("3.2 Execution Environment") column
>+<p>In the table below, the "3.3 EE" ("3.3 Execution Environment") column
> indicates the minimum Java class library requirements of each plug-in
>-for the 3.2 release, where the value is one of:</p>
>+for the 3.3 release, where the value is one of:</p>
> <table border="0" width="90%">
>   <tbody>
>     <tr>
>-      <td width="9%" align="center"><b>Entry</b></td>
>-      <td width="91%" align="left"><b>Meaning</b></td>
>+      <td align="center"><b>Entry</b></td>
>+      <td align="left"><b>Meaning</b></td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>M1.0</strong>
>+      <td>
>+      <div align="center"><strong>M1.0</strong></div>
>       </td>
>       <td>OSGi Minimum Execution Environment 1.0 - This is a subset of
>       the J2ME Foundation class libraries defined by OSGi to be the base
>@@ -1523,92 +1432,102 @@
>       details.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>M1.1</strong>
>+      <td width="9%">
>+      <div align="center"><strong>M1.1</strong></div>
>       </td>
>-      <td>OSGi Minimum Execution Environment 1.1 - This is a
>+      <td width="91%">OSGi Minimum Execution Environment 1.1 - This is a
>       subset of the J2ME Foundation class libraries defined by OSGi to
>       be the base for framework implementations. See the OSGi
>       specification for more details.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>F1.0</strong>
>+      <td>
>+      <div align="center"><strong>F1.0</strong></div>
>       </td>
>       <td>J2ME Foundation 1.0 - indicates that the plug-in can only be
>       run on Foundation 1.0 or greater. Note that with the exception of
>       some MicroEdition IO classes, Foundation 1.0 is a subset of J2SE
>-      1.3. <em>(see note below)</em></td>
>+      1.3.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>F1.1</strong>
>+      <td>
>+      <div align="center"><strong>F1.1</strong></div>
>       </td>
>       <td>J2ME Foundation 1.1 - indicates that the plug-in can only be
>       run on Foundation 1.1 or greater. Note that with the exception of
>       some MicroEdition IO classes, Foundation 1.1 is a subset of J2SE
>-      1.4. <em>(see note below)</em></td>
>+      1.4.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>1.2</strong>
>+      <td>
>+      <div align="center"><strong>1.2</strong></div>
>       </td>
>       <td>J2SE 1.2 - indicates that the plug-in can only be run on JSE
>       1.2 or greater.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>1.3</strong>
>+      <td>
>+      <div align="center"><strong>1.3</strong></div>
>       </td>
>       <td>J2SE 1.3 - indicates that the plug-in can only be run on JSE
>       1.3 or greater.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>1.4</strong>
>+      <td>
>+      <div align="center"><strong>1.4</strong></div>
>       </td>
>       <td>J2SE 1.4 - indicates that the plug-in can only be run on JSE
>       1.4 or greater.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>1.4/1.5</strong>
>+      <td>
>+      <div align="center"><strong>1.4/1.5</strong></div>
>       </td>
>       <td>Indicates that the plug-in can run on JSE
>       1.4 or greater, but provides enhanced functionality when run on J2SE 5.0.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>1.5</strong>
>+      <td>
>+      <div align="center"><strong>1.5</strong></div>
>       </td>
>       <td>J2SE 5.0 - indicates that the plug-in can only be run on JSE
>       5.0 or greater.</td>
>     </tr>
>     <tr>
>-      <td valign="top" align="center"><strong>n/a</strong></td>
>-      <td>Not applicable (e.g. documentation and source plug-ins).</td>
>+      <td>
>+      <div align="center"><strong>1.6</strong></div>
>+      </td>
>+      <td>J2SE 6.0 - indicates that the plug-in can only be run on JSE
>+      6.0 or greater.</td>
>+    </tr>
>+    <tr>
>+      <td align="center"><b>n/a</b></td>
>+      <td>Information not available, or not applicable (for example plug-ins that do not contain Java code)</td>
>     </tr>
>   </tbody>
> </table>
> <br>
>-<b>Note:</b> Plug-ins that are Foundation 1.0 should in fact list Foundation 1.0 AND J2SE1.3 in their execution environments.  
>-This is because Foundation 1.0 is not a proper subset of 1.3.  Listing them both will in essence say that the intersection of the 
>-two is valid for use in that plug-in. The situation is the same for Foundation 1.1 and J2SE1.4.
>-<p>
> <b>Table of minimum execution environments by plug-in.</b>
> <br>
> <br>
>-</p>
> <table border="1">
>   <tbody>
>     <tr>
>       <td width="290"><strong>Plug-in</strong></td>
>       <td width="60">
>-      <div align="center"><strong>3.2 EE</strong></div>
>+      <div align="center"><strong>3.3 EE</strong></div>
>       </td>
>     </tr>
>     <tr>
>-      <td>com.ibm.icu</td>
>+      <td>javax.servlet</td>
>       <td>
>       <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>com.ibm.icu.source</td>
>+      <td>javax.servlet.jsp</td>
>       <td>
>-      <div align="center">n/a</div>
>+      <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1618,9 +1537,27 @@
>       </td>
>     </tr>
>     <tr>
>+      <td>org.apache.commons.el</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.apache.commons.logging</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.apache.jasper</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.apache.lucene</td>
>       <td>
>-      <div align="center">1.3</div>
>+      <div align="center">n/a</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1644,7 +1581,7 @@
>     <tr>
>       <td>org.eclipse.core.boot</td>
>       <td>
>-      <div align="center">1.4</div>
>+      <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1684,6 +1621,12 @@
>       </td>
>     </tr>
>     <tr>
>+      <td>org.eclipse.core.net</td>
>+      <td>
>+      <div align="center">1.4</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.eclipse.core.resources</td>
>       <td>
>       <div align="center">1.4</div>
>@@ -1704,7 +1647,7 @@
>     <tr>
>       <td>org.eclipse.core.runtime.compatibility</td>
>       <td>
>-      <div align="center">F1.0</div>
>+      <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1738,12 +1681,54 @@
>       </td>
>     </tr>
>     <tr>
>+      <td>org.eclipse.equinox.app</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.eclipse.equinox.common</td>
>       <td>
>       <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>+      <td>org.eclipse.equinox.http.jetty</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.equinox.http.servlet</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.equinox.http.registry</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.equinox.jsp.jasper</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.equinox.jsp.jasper.registry</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.equinox.launcher</td>
>+      <td>
>+      <div align="center">F1.0</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.eclipse.equinox.preferences</td>
>       <td>
>       <div align="center">F1.0</div>
>@@ -1770,19 +1755,19 @@
>     <tr>
>       <td>org.eclipse.help.base</td>
>       <td>
>-      <div align="center">1.4</div>
>+      <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>       <td>org.eclipse.help.ui</td>
>       <td>
>-      <div align="center">1.4</div>
>+      <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>       <td>org.eclipse.help.webapp</td>
>       <td>
>-      <div align="center">1.4</div>
>+      <div align="center">F1.0</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1804,6 +1789,18 @@
>       </td>
>     </tr>
>     <tr>
>+      <td>org.eclipse.jdt.compiler.apt</td>
>+      <td>
>+      <div align="center">1.6</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.jdt.compiler.tool</td>
>+      <td>
>+      <div align="center">1.6</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.eclipse.jdt.core</td>
>       <td>
>       <div align="center">1.4</div>
>@@ -1848,7 +1845,7 @@
>     <tr>
>       <td>org.eclipse.jdt.junit.runtime</td>
>       <td>
>-      <div align="center">1.3</div>
>+      <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>@@ -1882,13 +1879,19 @@
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.jface.databinding</td>
>+      <td>org.eclipse.jface.text</td>
>       <td>
>       <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.jface.text</td>
>+      <td>org.eclipse.jsch.core</td>
>+      <td>
>+      <div align="center">1.4</div>
>+      </td>
>+    </tr>
>+    <tr>
>+      <td>org.eclipse.jsch.ui</td>
>       <td>
>       <div align="center">1.4</div>
>       </td>
>@@ -1972,6 +1975,12 @@
>       </td>
>     </tr>
>     <tr>
>+      <td>org.eclipse.pde.ui.templates</td>
>+      <td>
>+      <div align="center">1.4</div>
>+      </td>
>+    </tr>
>+    <tr>
>       <td>org.eclipse.platform</td>
>       <td>
>       <div align="center">F1.0</div>
>@@ -2034,13 +2043,13 @@
>     <tr>
>       <td>org.eclipse.swt</td>
>       <td bgcolor="#ffffff">
>-      <div align="center">F1.0</div>
>+      <div align="center">M1.0</div>
>       </td>
>     </tr>
>     <tr>
>       <td>org.eclipse.swt.*</td>
>       <td bgcolor="#ffffff">
>-      <div align="center">F1.0</div>
>+      <div align="center">M1.0</div>
>       </td>
>     </tr>
>     <tr>
>@@ -2146,12 +2155,6 @@
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.ui.intro.universal</td>
>-      <td>
>-      <div align="center">F1.0</div>
>-      </td>
>-    </tr>
>-    <tr>
>       <td>org.eclipse.ui.navigator</td>
>       <td>
>       <div align="center">1.4</div>
>@@ -2164,21 +2167,21 @@
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.ui.presentations.r21</td>
>+      <td>org.eclipse.ui.net</td>
>       <td>
>       <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.ui.views</td>
>+      <td>org.eclipse.ui.presentations.r21</td>
>       <td>
>       <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>org.eclipse.ui.views.properties.tabbed</td>
>+      <td>org.eclipse.ui.views</td>
>       <td>
>-      <div align="center">F1.0</div>
>+      <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>@@ -2242,19 +2245,19 @@
>       </td>
>     </tr>
>     <tr>
>-      <td>org.junit</td>
>+      <td>org.junit (old)</td>
>       <td>
>-      <div align="center">1.3</div>
>+      <div align="center">1.4</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>org.junit4</td>
>+      <td>org.junit (JUnit4)</td>
>       <td>
>       <div align="center">1.5</div>
>       </td>
>     </tr>
>     <tr>
>-      <td>startup.jar</td>
>+      <td>org.mortbay.jetty</td>
>       <td>
>       <div align="center">F1.0</div>
>       </td>

Actions: View | Diff

Attachments on bug 185753: 66564 | 66706 | 66939 | 68276 | 68391 | 68798 | 70402 | 70408 | 70439 | 70543 | 70722 | 71025 | 71061