<title>Eclipse Project Release Notes 3.2</title>

<title>Eclipse Project Release Notes 3.3</title>

</p>

 </p><p> 

<p>  

  In general, the 3.3 release of the Eclipse Project is developed on a

  With the exception of a small set of features that

  mix of Java 1.4 and Java5 VMs. As such, the Eclipse Project SDK as

  actually require Java SE 5 APIs (in particular, the support for

  a whole is targeted at both 1.4 and Java5 VMs, with full functionality 

  Annotation Processing and JUnit 4), the 3.2 release of the Eclipse

  available for 1.4 level development everywhere, and new Java5 specific

  Project runs against version 1.4 of the Java 2 Platform.

  capabilities available when running on a Java5 VM. Similarly, in cases

  As such, the Eclipse Project SDK as a whole is targeted at both

  where support has been added for Java6 specific features (e.g. JSR-199,

  1.4 and Java5 VMs, with full functionality available for 1.4 level

  JSR-269, etc.) Java6 VMs are required.

  development everywhere, and new Java5 specific capabilities available

</p><p>

  when running on a Java5 VM.

  many operating environments beyond the reference platforms we test. However, 

  many operating environments beyond the reference platforms we test, including

  since we do not systematically test them we cannot vouch for them. Problems 

  those using Java6 VMs. However, since we do not systematically test them we

  encountered when running Eclipse on a non-reference platform that cannot be recreated 

  cannot vouch for them. Problems encountered when running Eclipse on a non-reference

  on any reference platform are given lower priority than problems with running 

  platform that cannot be recreated on any reference platform will be given lower

  Eclipse on a reference platform.</p>

  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>

<p>

<table summary="Eclipse Reference Platforms" style="width: 821px;" border="1">

The Eclipse SDK 3.3 is tested and validated on the following reference platforms:</p>

  <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">

        Sun Java 2 Standard Edition 1.4.2_10<br>for Linux x86</td>

<center>

    </tr>

<table border="1" cellpadding="2" cellspacing="2" width="80%" summary="Eclipse Reference Platforms">

<tbody>

    <tr>

      <td width="205">SUSE Linux Enterprise Server</td>

<tr align="center">

      <td width="59">9</td>

<td><b>Reference Platforms</b></td>

      <td width="76">Intel x86</td>

</tr>

      <td width="59">GTK</td>

<tr><td>

      <td width="453">

<b>Microsoft Windows Vista, x86-32, Win32</b> running (any of):

        IBM 32-bit SDK for Linux on Intel architecture,<br>Java 2 Technology Edition 1.4.2 service release 3

<ul>

      </td>

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Microsoft Windows</li>

    </tr>

<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>

    <tr>

</ul>

      <td width="205">Sun Solaris</td>

</td></tr>

      <td width="59">10</td>

      <td width="76">SPARC</td>

<tr><td>

      <td width="59">GTK</td>

<b>Microsoft Windows XP, x86-32, Win32</b> running (any of):

      <td width="453">

<ul>

        Sun Java 2 Standard Edition 1.4.2_10<br>for Solaris SPARC</td>

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Microsoft Windows</li>

    </tr>

<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR4</li>

<li>BEA JRockit 5.0, for Microsoft Windows</li>

    <tr>

<li>Sun Java 2 Standard Edition 1.4.2_14 for Microsoft Windows</li>

      <td width="205">HP HP-UX</td>

<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>

<tr><td>

      <td width="76">hp9000<br>PA-RISC</td>

<b>Red Hat Enterprise Linux 4.0 update 2, x86-32, GTK</b> running (any of):

      <td width="59">Motif</td>

<ul>

      <td width="453">

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86</li>

        HP-UX JDK for the Java 2 Platform Standard Edition for 1.4.2_09

<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR4</li>

      </td>

<li>BEA JRockit 5.0, for Linux x86</li>

    </tr>

<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>

    <tr>

<b>SUSE Linux Enterprise Server 10, x86-32, GTK</b> running (any of):

      <td width="205">IBM AIX 5L</td>

<ul>

      <td width="59">5.2</td>

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86</li>

      <td width="76">Power</td>

<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR4</li>

      <td width="59">Motif</td>

</ul>

      <td width="453">

</td></tr>

        IBM 32-bit SDK for AIX,<br>Java 2 Technology Edition 1.4.2 service release 3

      </td>

    </tr>

<tr><td>

<b>Red Hat Enterprise Linux 4.0 update 2, x86-64, GTK</b> running:

    <tr>

<ul>

      <td width="205">Apple Mac OS X</td>

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Linux x86_64</li>

      <td width="59">10.4</td>

</ul>

      <td width="76">Power, Intel x86</td>

</td></tr>

      <td width="59">Carbon</td>

      <td width="453">

        Java 2 Platform Standard Edition (J2SE) 1.4.2<br>service release 2 for Tiger

<tr><td>

      </td>

<b>Sun Solaris 10, SPARC, GTK</b> running:

    </tr>

<ul>

<li>Sun Java 2 Standard Edition 5.0 Update 11 for Solaris SPARC</li>

    <tr>

</ul>

      <td width="205">Red Hat Enterprise Linux</td>

</td></tr>

      <td width="59">WS 4</td>

      <td width="76">Power</td>

      <td width="59">GTK</td>

<tr><td>

      <td width="453">

<b>IBM AIX 5.3, Power, Motif 2.1</b> running:

        IBM 32-bit SDK for Linux on pSeries architecture, <br>Java 2 Technology Edition 1.4.2 service release 3

<ul>

      </td>

<li>IBM 32-bit SDK, Java 2 Technology Edition 5.0, SR4</li>

    </tr>

</ul>

</td></tr>

    <tr>

<tr><td>

      <td width="205">SUSE Linux Enterprise Server</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>

<tr><td>

      <td width="76">Power</td>

<b>SUSE Linux Enterprise Server 10, Power, GTK</b> running:

      <td width="59">GTK</td>

<ul>

      <td width="453">

<li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 1.4.2 service release 7</li>

        IBM 32-bit SDK for Linux on pSeries architecture, <br>Java 2 Technology Edition 1.4.2 service release 3

</ul>

      </td>

</td></tr>

    </tr>

<tr><td>

    <tr>

<b>Apple Mac OS X 10.4, Universal, Carbon</b> running:

      <td width="205">SUSE Linux Enterprise Server</td>

<ul>

      <td width="59">9</td>

<li>Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4 for Tiger</li>

      <td width="76">Power</td>

</ul>

      <td width="59">GTK</td>

</td></tr>

      <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>

</tbody>

  </tbody>

<p>Because Java 1.4.2 platforms are used for most Eclipse development,

<dl>

  in general, 1.4.2 platforms are listed here. Of course, the teams doing Java 5 based

<dt><em>Caveat: Using IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR4 on Vista</em></dt>

  development use Java 5 platforms, and the specific ones that they test on

<dd>Although we expect this to be fixed in IBM Java5 SR5, there is currently a conflict between

  are also included. <i>We expect that Eclipse works fine on other Java 5 VMs

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

  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 

  Photon window system, and IBM J9 VM version 2.0. Eclipse 3.2 on Windows or Linux 

  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.2 is unavailable on QNX 

  can be used to cross-develop QNX applications. (Eclipse 3.3 is unavailable on QNX 

  because there is currently no 1.4 J2SE for QNX.)</p>

  because there is currently no 1.5 J2SE for QNX.)</p>

<p></p>

  <p></p>

<p>The Eclipse Platform is designed as the basis for internationalized products.

The user interface elements provided by the Eclipse SDK components, including

<p>The Eclipse SDK is designed as the basis for internationalized products. 

dialogs and error messages, are externalized. The English strings are provided

  The user interface elements provided by the Eclipse SDK components, including 

as the default resource bundles.</p>

  dialogs and error messages, are externalized. The English strings are provided 

<p>Latin-1 locales are supported by the Eclipse SDK on all of the above

  as the default resource bundles.</p>

operating environments; DBCS locales are supported by the Eclipse SDK on the

Windows, GTK, and Motif window systems; BIDI locales are supported by the

<p>Latin-1 locales are supported by the Eclipse SDK on all of the above 

Eclipse SDK only on Windows operating environments.

  operating environments; DBCS locales are supported by the Eclipse SDK 

<p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, 

  on the Windows, GTK, and Motif window systems; BIDI locales are supported by 

  on Windows XP and 2000, and Linux. 

  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>

<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>

<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>Eclipse 3.3 is compatible with Eclipse 3.2.</p>

<p><b>API Contract Compatibility:</b> Eclipse SDK 3.2 is upwards contract-compatible 

<p>

  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 

  <strong>API Contract Compatibility:</strong> Eclipse SDK 3.3 is upwards contract-compatible 

  3.2 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension 

  with Eclipse SDK 3.2 except in those areas noted in the 

  points will need to be ported to Eclipse SDK 3.2 APIs. Downward contract compatibility 

  <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">

  is not supported. There is no guarantee that compliance with Eclipse SDK 3.2 

    <em>Eclipse 3.3 Plug-in Migration Guide</em>

  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 

  </a>. 

  Java-based APIs</a></i> for a discussion of the kinds of API changes that maintain 

  Programs that use affected APIs and extension points will need to be ported to

  contract compatibility.</p>

  Eclipse SDK 3.3 APIs. Downward contract compatibility is not supported.

  There is no guarantee that compliance with Eclipse SDK 3.3 

<p><b>Binary (plug-in) Compatibility:</b> Eclipse SDK 3.2 is upwards binary-compatible 

  APIs would ensure compliance with Eclipse SDK 3.2 APIs. Refer to 

  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 

  <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">

  3.2 Plug-in Migration Guide</em></a>. Downward plug-in compatibility is not 

    <em>Evolving Java-based APIs</em>

  supported. Plug-ins for Eclipse SDK 3.2  are not usable in Eclipse SDK 3.1. 

  </a> for a discussion of the kinds of API changes that maintain contract compatibility.

  Refer to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving 

</p>

  Java-based APIs</a></i> for a discussion of the kinds of API changes that maintain 

<p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 3.3 is upwards binary-compatible 

  binary compatibility. 

  with Eclipse SDK 3.2 except in those areas noted in the

</p><p><b>Source Compatibility:</b> Eclipse SDK 3.2 is upwards source-compatible 

  <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">

  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 

    <em>Eclipse 3.3 Plug-in Migration Guide</em>

  3.2 Plug-in Migration Guide</em></a>. This means that source files written to 

  </a>. 

  use Eclipse SDK 3.1 APIs might successfully compile and run against Eclipse 

  Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.3

  SDK 3.2 APIs, although this is not guaranteed. Downward source compatibility 

  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 

</p><p><b>Workspace Compatibility:</b> Eclipse SDK 3.2 is upwards workspace-compatible 

</p>

  with Eclipse SDK 3.1 unless noted. This means that workspaces and projects created 

<p><strong>Workspace Compatibility:</strong> Eclipse SDK 3.3 is upwards workspace-compatible 

  with Eclipse SDK 3.1 or 3.0 can be successfully opened by Eclipse SDK 3.2 and 

  with Eclipse SDK 3.2 unless noted. This means that workspaces and projects created 

  upgraded to a 3.2 workspace. This includes both hidden metadata, which is localized 

  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 

  SDK 3.2 should provide similar upwards compatibility for their hidden and visible 

  SDK 3.3 should provide similar upwards compatibility for their hidden and visible 

  workspace metadata created by earlier versions; 3.2 plug-in developers are responsible 

  workspace metadata created by earlier versions; 3.3 plug-in developers are responsible 

  for ensuring that their plug-ins recognize 3.1, 3.0, 2.1, and 2.0 metadata and 

  for ensuring that their plug-ins recognize 3.2, 3.1, 3.0, 2.1, and 2.0 metadata and 

  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 

  (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 

<p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes, and

<h3>Compatibility of Release 3.2 with 3.0, 2.1 and 2.0</h3>

  certainly everything in a package with "internal" in its name, are

<p>Since Eclipse 3.1 is compatible with Eclipse 3.0, 2.1 and 2.0 in most regards, and 

  considered implementation details which may vary between operating environment

  Eclipse 3.2 is compatible with 3.1, it follows that 3.2 is also compatible with 

  and are subject to change without notice. Client plug-ins that directly depend

  3.0, 2.1 and 2.0 in most aspects. If you are upgrading directly from 3.0, 2.1 or 2.0, 

  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, 

  <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>

  <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 3.2 requires 

  <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 3.3 requires 

<h3>6.1 Interoperability of Release 3.2 and 3.1</h3>

<h3>6.1 Interoperability of Release 3.3 with previous releases</h3>

<h4>Sharing projects between heterogeneous Eclipse 3.2 and 3.1</h4>

<h4>Sharing projects between heterogeneous Eclipse 3.3 and 3.2</h4>

with shared metadata. However, when some developers are working in Eclipse 3.2

with shared metadata. However, when some developers are working in Eclipse 3.3

while others are working in Eclipse 3.1, there are no such guarantees.

while others are working in Eclipse 3.2, there are no such guarantees.

This section provides advice for what to do and to not do. It addresses the

This section provides advice for what to do and not to do. It addresses the

<p>The typical failure mode is noticed by the 3.2 user. 3.2 metadata is lost

<p>The typical failure mode is noticed by the 3.3 user. 3.3 metadata is lost

when a 3.1 user saves changes and then commits the updated metadata files to the

when a 3.2 user saves changes and then commits the updated metadata files to the

  <li>A user working in Eclipse 3.2 creates or modifies a project in a way that

  <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.2-specific

    results in changes to a shared metadata file that rely on 3.3-specific

  <li>Another user working in Eclipse 3.1 shares this project from the same

  <li>Another user working in Eclipse 3.2 shares this project from the same

    repository. The 3.2-specific information in the shared metadata file is not

    repository. The 3.3-specific information in the shared metadata file is not

    understood by Eclipse 3.1, and is generally discarded or ignored without

    understood by Eclipse 3.2, and is generally discarded or ignored without

    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

  <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

Eclipse 3.2 and 3.1:</p>

Eclipse 3.3 and 3.1:</p>

  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,

  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

<h4>Using Eclipse 3.2 to develop plug-ins that work in Eclipse 3.1</h4>

<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.2 to develop a plug-in 

<p>It is also possible (and reasonable) to use Eclipse 3.3 to develop a plug-in 

  intended to work in Eclipse 3.1 or earlier. Use the <b>Plug-in Development &gt; 

  intended to work in Eclipse 3.2 or earlier. Use the <b>Plug-in Development &gt; 

  3.1 install. This ensures that the code for your plug-in is being compiled and 

  3.2 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 

  tested against Eclipse 3.2 APIs, extension points, and plug-ins. (The above 

<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

<p>(c) Copyright IBM Corp. and others 2006</p>

<p>(c) Copyright IBM Corp. and others 2007</p>

<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

for the 3.2 release, where the value is one of:</p>

for the 3.3 release, where the value is one of:</p>

      <td width="9%" align="center"><b>Entry</b></td>

      <td align="center"><b>Entry</b></td>

      <td width="91%" align="left"><b>Meaning</b></td>

      <td align="left"><b>Meaning</b></td>

      <td valign="top" align="center"><strong>M1.0</strong>

      <td>

      <div align="center"><strong>M1.0</strong></div>

      <td valign="top" align="center"><strong>M1.1</strong>

      <td width="9%">

      <div align="center"><strong>M1.1</strong></div>

      <td>OSGi Minimum Execution Environment 1.1 - This is a

      <td width="91%">OSGi Minimum Execution Environment 1.1 - This is a

      <td valign="top" align="center"><strong>F1.0</strong>

      <td>

      <div align="center"><strong>F1.0</strong></div>

      1.3. <em>(see note below)</em></td>

      1.3.</td>

      <td valign="top" align="center"><strong>F1.1</strong>

      <td>

      <div align="center"><strong>F1.1</strong></div>

      1.4. <em>(see note below)</em></td>

      1.4.</td>

      <td valign="top" align="center"><strong>1.2</strong>

      <td>

      <div align="center"><strong>1.2</strong></div>

      <td valign="top" align="center"><strong>1.3</strong>

      <td>

      <div align="center"><strong>1.3</strong></div>

      <td valign="top" align="center"><strong>1.4</strong>

      <td>

      <div align="center"><strong>1.4</strong></div>

      <td valign="top" align="center"><strong>1.4/1.5</strong>

      <td>

      <div align="center"><strong>1.4/1.5</strong></div>

      <td valign="top" align="center"><strong>1.5</strong>

      <td>

      <div align="center"><strong>1.5</strong></div>

      <td valign="top" align="center"><strong>n/a</strong></td>

      <td>

      <td>Not applicable (e.g. documentation and source plug-ins).</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>

      <div align="center"><strong>3.2 EE</strong></div>

      <div align="center"><strong>3.3 EE</strong></div>

      <td>com.ibm.icu</td>

      <td>javax.servlet</td>

      <td>com.ibm.icu.source</td>

      <td>javax.servlet.jsp</td>

      <div align="center">n/a</div>

      <div align="center">F1.0</div>

      <div align="center">1.3</div>

      <div align="center">n/a</div>

      <div align="center">1.4</div>

      <div align="center">F1.0</div>

      <div align="center">F1.0</div>

      <div align="center">1.4</div>

      <div align="center">1.4</div>

      <div align="center">F1.0</div>

      <div align="center">1.4</div>

      <div align="center">F1.0</div>

      <div align="center">1.4</div>

      <div align="center">F1.0</div>

      <div align="center">1.3</div>

      <div align="center">1.4</div>

      <td>org.eclipse.jface.databinding</td>

      <td>org.eclipse.jface.text</td>

      <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>

      <div align="center">F1.0</div>

      <div align="center">M1.0</div>

      <div align="center">F1.0</div>

      <div align="center">M1.0</div>

      <td>org.eclipse.ui.presentations.r21</td>

      <td>org.eclipse.ui.net</td>

      <td>org.eclipse.ui.views</td>

      <td>org.eclipse.ui.presentations.r21</td>

      <td>org.eclipse.ui.views.properties.tabbed</td>

      <td>org.eclipse.ui.views</td>

      <div align="center">F1.0</div>

      <div align="center">1.4</div>

      <td>org.junit</td>

      <td>org.junit (old)</td>

      <div align="center">1.3</div>

      <div align="center">1.4</div>

      <td>org.junit4</td>

      <td>org.junit (JUnit4)</td>

      <td>startup.jar</td>

      <td>org.mortbay.jetty</td>