Google Git
Sign in
eclipse / www.eclipse.org / org / 8b043e2af493210210e491f1249142f231b9c76f / . / councils / roadmap_v4_0 / eclipse_plan.html
blob: 68b79ebe56745807fa8df7f47bbdc8448ff76c12 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title>Project Plan - eclipse</title><meta name="author" content="Bjorn Freeman-Benson" />
<meta name="keywords" content="" /><link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/small.css" title="small" /><link rel="alternate stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/large.css" title="large" /><link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/visual.css" media="screen" /><link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/layout.css" media="screen" />
<!--[if IE]> <link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/ie_style.css" media="screen"/> <![endif]-->
<!--[if IE 6]> <link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/ie6_style.css" media="screen"/> <![endif]-->
<link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/print.css" media="print" />
<link rel="stylesheet" type="text/css" href="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/css/header.css" media="screen" />
<script type="text/javascript" src="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/styleswitcher.js"></script>
</head>
<body>
<div id="header">
<div id="header-graphic" class="eclipse-main">
<a href="http://www.eclipse.org/"><img src="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg" alt="" /></a><h1>Eclipse</h1>
</div>
<div id="header-global-holder" class="eclipse-main-global">
<div id="header-global-links"><ul>
<li><a href="http://www.eclipse.org/org/foundation/contact.php" class="first_one">Contact</a></li><li><a href="http://www.eclipse.org/legal/">Legal</a></li>
</ul>
</div>
<div id="header-icons">
<a href="http://www.youtube.com/user/EclipseFdn" target="_blank"><img src="/eclipse.org-common/themes/Phoenix/images/Icon_Live.png" width="28" height="28" alt="Eclipse YouTube Channel" title="Eclipse YouTube Channel" /></a>
<a href="http://www.eclipseplugincentral.com"><img src="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/Icon_plugin.png" width="28" height="28" alt="Eclipse Plugin Central" title="Eclipse Plugin Central" /></a>
<a href="http://www.planeteclipse.org"><img src="http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/Icon_planet.png" width="28" height="28" alt="Planet Eclipse" title="Planet Eclipse" /></a>
</div>
</div></div><div id="header-menu"><div id="header-nav">
<ul>
<li><a class="first_one" href="http://www.eclipse.org/" target="_self">Home</a></li>
<li><a href="http://www.eclipse.org/users/" target="_self">Users</a></li>
<li><a href="http://www.eclipse.org/membership/" target="_self">Members</a></li>
<li><a href="http://www.eclipse.org/committers/" target="_self">Committers</a></li>
<li><a href="http://www.eclipse.org/downloads/" target="_self">Downloads</a></li>
<li><a href="http://www.eclipse.org/resources/" target="_self">Resources</a></li>
<li><a href="http://www.eclipse.org/projects/" target="_self">Projects</a></li>
<li><a href="http://www.eclipse.org/org/" target="_self">About Us</a></li>
</ul>
</div>
<div id="header-utils">
<form action="http://www.google.com/cse" id="searchbox_017941334893793413703:sqfrdtd112s">
<input type="hidden" name="cx" value="017941334893793413703:sqfrdtd112s" />
<input type="text" name="q" size="25" />
<input type="submit" name="sa" value="Search" />
</form>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=searchbox_017941334893793413703%3Asqfrdtd112s&lang=en"></script> <ul>
<li class="text_size"><a class="smallText" title="Small Text" href="#" onclick="setActiveStyleSheet('small');return false;">A</a> <a class="largeText" title="Large Text" href="#" onclick="setActiveStyleSheet('large');return false;">A</a></li>
</ul>
</div></div><div id="leftcol">
<ul id="leftnav">
<li style="background-image: url(/eclipse.org-common/themes/Phoenix/images/leftnav_fade.jpg); background-repeat: repeat-x; border-style: none;"><br /><br /><br /><br /><br /><br /><br /><br />
</li>
</ul>
</div>
<div id="container"><style>
h2 {
border-bottom: 2px solid gray;
}
h3 {
border-bottom: 1px dotted gray;
}
</style>
<div xmlns="http://www.w3.org/1999/xhtml" id="rendered-plan">
<div id="maincontent">
<div id="midcolumn"><h1><span style="font-size: 140%">Project Plan For
<a href="http://www.eclipse.org/projects/project_summary.php?projectid=eclipse">Eclipse Project</a></span>, version Galileo</h1><div id="toc"><p><a name="toc"><strong>Table of Contents</strong></a></p><ul><li><a href="#introduction">Introduction</a></li><li><a href="#release_deliverables">
Release Deliverables
</a></li><li><a href="#release_milestones">
Release Milestones
</a></li><li><a href="#target_environments">
Target Environments
</a></li><li><a href="#compatibility">
Compatibility with Previous Releases
</a></li><li><a href="#themes_and_priorities">
Themes and Priorities
</a></li><li><a href="#appendix">
Appendix
</a></li></ul></div><h2><a name="introduction">Introduction</a></h2><div>
<p>
Last revised 14:30 ET Oct 10, 2008
</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 feature and API set for the next feature release
of the Eclipse SDK after 3.4, designated release 3.5.
</p>
<p>Plans do not materialize out of nowhere, nor are they entirely static. To
ensure the planning process is transparent and open to the entire Eclipse community,
we (the Eclipse Project PMC) post plans in an embryonic form and revise them
throughout the release cycle. </p>
<p>The first part of the plan deals with the important matters of release deliverables,
release milestones, target operating environments, and release-to-release compatibility.
These are all things that need to be clear for any release, even if no features
were to change. </p>
<p>The remainder of the plan consists of plan items for all of the sub-projects
under the top level Eclipse Project. Each plan item covers a feature or API
that is to be added to the Eclipse Project deliverables, or some aspect of
the Eclipse Project that is to be improved. Each plan item has its own entry
in the Eclipse bugzilla database, with a title and a concise summary (usually
a single paragraph) that explains the work item at a suitably high enough level
so that everyone can readily understand what the work item is without having
to understand the nitty-gritty detail. </p>
<p>Not all plan items represent the same amount of work; some may be quite large,
others, quite small. Some plan items may involve work that is localized to
a single component; others may involve coordinated changes to several components;
other may pervade the entire SDK. Although some plan items are for work that
is more pressing than others, the plan items appear in no particular order. </p>
<p>With the previous release as the starting point, this is the plan for how
we will enhance and improve it. Fixing bugs, improving test coverage, documentation,
examples, performance tuning, usability, etc. are considered routine ongoing
maintenance activities and are not included in this plan unless they would
also involve a significant change to the API or feature set, or involve a significant
amount of work. The intent of the plan is to account for all interesting feature
work. </p>
<p>The current status of each plan item is noted: </p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are considering
addressing for the release. Although we are actively investigating it, we
are not yet in a position to commit to it, or to say that we won't be able
to address it. After due consideration, a proposal will either be committed
or deferred.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it
in to this release for some reason is marked as deferred with a brief note
as to why it was deferred. Deferred plan items may resurface as committed
plan items at a later point.</li>
</ul>
</div><h2><a name="release_deliverables">Release Deliverables</a></h2><div>
<p>The release deliverables have the same form as previous releases, namely: </p>
<ul>
<li>Source code release for all Eclipse Project deliverables, available as
versions tagged "R3_5" in the Eclipse Project <a href="http://dev.eclipse.org/viewcvs/">CVS
repository</a>.</li>
<li>Eclipse SDK (runtime binary and SDK for Equinox[*], Platform, JDT, and PDE) (downloadable).</li>
<li>Eclipse Platform (runtime binary and SDK for the Equinox[*] and Platform only) (downloadable).</li>
<li>Eclipse RCP (runtime binary and SDK for the Rich Client Platform) (downloadable).</li>
<li>Eclipse JDT (runtime binary and SDK for the Java Development Tools) (downloadable).</li>
<li>Eclipse PDE (runtime binary and SDK for the Plug-in Development Environment) (downloadable).</li>
<li>Eclipse SDK Examples (downloadable).</li>
<li>SWT distribution (downloadable).</li>
</ul>
<p>* The <a href="http://www.eclipse.org/equinox/">Equinox Project</a> is part of the top level
<a href="http://www.eclipse.org/rt/">RT Project</a>. A significant portion of the Equinox
deliverables are consumed and redistributed as part of the Eclipse Project's SDK, Platform,
and RCP deliverables.</p>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="release_milestones">Release Milestones</a></h2><p>
Release milestones will be occurring at roughly 6 week intervals, and will be aligned with the
<a href="http://wiki.eclipse.org/Galileo_Simultaneous_Release">
Galileo Simultaneous Release</a> train.</p><table border="1" align="center"><tr><td><b>M1</b></td><td>08/08/2008</td><td><div>3.5M1</div></td></tr><tr><td><b>M2</b></td><td>09/19/2008</td><td><div>3.5M2</div></td></tr><tr><td><b>M3</b></td><td>10/31/2008</td><td><div>3.5M3</div></td></tr><tr><td><b>M4</b></td><td>12/12/2008</td><td><div>3.5M4</div></td></tr><tr><td><b>M5</b></td><td>01/30/2009</td><td><div>3.5M5</div></td></tr><tr><td><b>M6</b></td><td>03/12/2009</td><td><div>3.5M6 (API Freeze)</div></td></tr><tr><td><b>M7</b></td><td>05/01/2009</td><td><div>3.5M7 (Feature Freeze)</div></td></tr><tr><td><b>RC1</b></td><td>05/15/2009</td><td><div>3.5RC1</div></td></tr><tr><td><b>RC2</b></td><td>05/29/2009</td><td><div>3.5RC2</div></td></tr><tr><td><b>RC3</b></td><td>06/05/2009</td><td><div>3.5RC3</div></td></tr><tr><td><b>RC4</b></td><td>06/12/2009</td><td><div>3.5RC4</div></td></tr></table><div>
<p>Individual, milestone level plans for the components that make up the Eclipse Project can be found
on the <a href="http://wiki.eclipse.org/Eclipse/Galileo_Plan">Eclipse Project Galileo Plan page</a>
on the Eclipse wiki.</p>
<p>Our target is to complete 3.5 in late June 2009, in alignment with Galileo.
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>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="target_environments">Target Environments</a></h2><div>
<p>In order to remain current, each Eclipse Project 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 are targeted 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>In general, the 3.5 release of the Eclipse Project is developed on a mix
of Java 1.4, Java5 and Java6 VMs. As such, the Eclipse SDK as a whole
is targeted at all modern, desktop Java VMs. Full functionality is available for
1.4 level development everywhere, and extended development capabilities are made
available on the VMs that support them.</p>
<p><a href="#Appendix1">Appendix 1</a> contains a table that indicates the class
library level required for each bundle.</p>
<p>There are many different implementations of the Java Platform running atop
a variety of operating systems. We focus our 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 will
be given lower priority than problems with running Eclipse on a reference platform.</p>
<p>Eclipse 3.5 is tested and validated on the following reference platforms
(this list is updated over the course of the release cycle):</p>
<table border="1" cellpadding="2" cellspacing="2" width="80%" summary="Reference Platforms">
<tr align="center">
<td><b>Reference Platforms</b></td>
</tr>
<tr>
<td><b>Microsoft Windows Vista, x86-32, Win32</b> running (any of):
<ul>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows</li>
<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
<li>BEA JRockit 27.4.0, for Microsoft Windows</li>
</ul></td>
</tr>
<tr>
<td><b>Microsoft Windows XP, x86-32, Win32</b> running (any of):
<ul>
<li>Sun Java 2 Standard Edition 6.0 Update 4 for Microsoft Windows</li>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows</li>
<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
<li>BEA JRockit 27.4.0, for Microsoft Windows</li>
<li>Sun Java 2 Standard Edition 1.4.2_16 for Microsoft Windows</li>
<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 1.4.2 SR10</li>
</ul></td>
</tr>
<tr>
<td><b>Red Hat Enterprise Linux 5.0, x86-32, GTK</b> running (any of):
<ul>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Linux x86</li>
<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li>
<li>BEA JRockit 27.4.0, for Linux x86</li>
<li>Sun Java 2 Standard Edition 1.4.2_16 for Linux x86</li>
<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 1.4.2 SR10</li>
</ul></td>
</tr>
<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 14 for Linux x86</li>
<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Microsoft Windows Vista, x86-64, Win32</b> running (any of):
<ul>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows (AMD64/EM64T)</li>
<li>IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Microsoft Windows XP Professional x64 Edition, x86-64, Win32</b> running (any of):
<ul>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows (AMD64/EM64T)</li>
<li>IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<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 14 for Linux x86_64</li>
</ul></td>
</tr>
<tr>
<td><b>Sun Solaris 10, SPARC, GTK</b> running:
<ul>
<li>Sun Java 2 Standard Edition 5.0 Update 14 for Solaris SPARC</li>
</ul></td>
</tr>
<tr>
<td><b>HP-UX 11i v2, ia64, Motif 2.1, GTK</b> running:
<ul>
<li>HP-UX Java 2 Standard Edition 5.0 Update 7 for Itanium</li>
</ul></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, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Red Hat Enterprise Linux 5.0, Power, GTK</b> running:
<ul>
<li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b</li>
</ul></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 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Apple Mac OS X 10.5, Universal, Carbon</b> running:
<ul>
<li>Apple Java for Mac OS X 10.5, Update 1</li>
</ul></td>
</tr>
<tr>
<td><b>Apple Mac OS X 10.5, Universal, Cocoa</b> running:
<ul>
<li>Apple Java for Mac OS X 10.5, Update 1</li>
</ul></td>
</tr>
</table>
<p>As stated above, <i>we expect that Eclipse works fine on other current
Java VM and OS versions but we cannot flag these as reference platforms without
significant community support for testing them.</i></p>
</div><h3>Internationalization</h3>
<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 and DBCS locales are supported by the Eclipse SDK on all reference platforms;
BIDI locales are supported by the Eclipse SDK everywhere but on Motif.</p>
<p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard,
on Windows XP and 2000, Linux/GTK and the Macintosh.</p>
<p>German and Japanese locales are tested.</p>
<p><a href="#toc">Table of Contents</a></p><h2><a name="compatibility">Compatibility with Previous Releases</a></h2><div>
<h3>Compatibility of Release 3.5 with 3.4</h3>
<p>Eclipse 3.5 will be compatible with Eclipse 3.4 (and all earlier 3.x versions).</p>
<p><strong>API Contract Compatibility:</strong> Eclipse SDK 3.5 will be upwards
contract-compatible with Eclipse SDK 3.4 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_5_porting_guide.html" target="_top">
<em>Eclipse 3.5 Plug-in Migration Guide</em>
</a>. Programs that use affected APIs and extension points will need to be ported
to Eclipse SDK 3.5 APIs. Downward contract compatibility
is not supported. There is no guarantee that compliance with Eclipse SDK 3.5
APIs would ensure compliance with Eclipse SDK 3.4 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.5 will be upwards
binary-compatible with Eclipse SDK 3.4 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_5_porting_guide.html" target="_top">
<em>Eclipse 3.5 Plug-in Migration Guide</em>
</a>. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK
3.5 will not be usable in Eclipse SDK 3.4. 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.5 will be upwards source-compatible
with Eclipse SDK 3.4 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_5_porting_guide.html" target="_top">
<em>Eclipse 3.5 Plug-in Migration Guide</em>
</a>. This means that source files written
to use Eclipse SDK 3.4 APIs might successfully compile and run against Eclipse
SDK 3.5 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><strong>Workspace Compatibility:</strong> Eclipse SDK 3.5 will be upwards
workspace-compatible with ealier 3.x versions of the Eclipse SDK unless noted.
This means that workspaces and projects created with Eclipse SDK 3.4 .. 3.0 can be successfully
opened by Eclipse SDK 3.5 and upgraded to a 3.5 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.5 should provide similar upwards compatibility
for their hidden and visible workspace metadata created by earlier versions;
3.5 plug-in developers are responsible for ensuring that their plug-ins recognize
metadata from earlier versions 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.5 will be unusable with a product based an earlier
version of Eclipse. Visible metadata files created (or overwritten) by Eclipse
3.5 will generally be unusable with earlier versions of Eclipse. </p>
<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>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="themes_and_priorities">Themes and Priorities</a></h2><div>
<p>The plan items listed below were defined according to contributor requirements and the Eclipse
<a href="http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities">Themes and Priorities</a>
set forth by the Eclipse Requirements Council. Each plan item covers a feature or API that is
to be added to the Eclipse Project deliverables, or some aspect of the Eclipse Project that is
to be improved. Each plan item has its own entry in the Eclipse bugzilla database, with a title
and a concise summary (usually a single paragraph) that explains the work item at a suitably
high enough level so that everyone can readily understand what the work item.</p>
<p> Although there are four projects under the top-level Eclipse Project, there
is a significant amount of commonality and shared effort between them. In general,
many plan items involve coordinated changes to multiple components, and thus
attempting to separate the items into sections based on sub-project leads to
artificial distinctions between them (e.g., Platform Text vs. JDT Text, Platform
Debug vs. JDT Debug, etc.). As such, this plan covers the work of all projects
under the top level Eclipse Project.</p>
<p>Not all plan items represent the same amount of work; some may be quite
large, others, quite small. Although some plan items are for work that is
more pressing than others, the plan items appear in no particular order.
See the corresponding bugzilla items for up-to-date status information on
ongoing work and planned delivery milestones.</p>
<p>The current status of each plan item is noted:</p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release. In bugzilla, this is reflected by
having a concrete target milestone assigned.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are
considering addressing for the release. Although we are actively
investigating it, we are not yet in a position to commit to it, or to say
that we won't be able to address it. After due consideration, a proposal
will either be committed or deferred. In bugzilla, such items are reflected
by having a target milestone "3.5" or "---" assigned.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it in
to this release for some reason is marked as deferred with a brief note as
to why it was deferred. Deferred plan items may resurface as committed plan
items at a later point. In bugzilla, such items are reflected by having
a target milestone "Future" assigned.</li>
</ul>
</div><h3>Platforms</h3><p>This work is focused on ensuring that Eclipse takes full advantage of all
capabilities of the underlying technologies that it is based on, be they
operating system, window system, Java or other. This includes support
for native accessibility, internationalization and localization capabilities.
</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><strong>Support Cocoa on Mac OS X.</strong>
Apple GUI development is moving from Carbon to Cocoa. We will support the Eclipse
SDK running on Mac OS Cocoa (including 64-bit Java6), to ensure that Eclipse
continues to be a first-class application delivery and development platform on the
Mac. <em>(Note that completing this work will require investment from the Equinox
Project, in addition to the work here.)</em> [SWT, Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252644">252644</a>)</li>
<li><strong>BIDI improvements.</strong>
We will continue to invest in improving in our BIDI support, to ensure that
Eclipse is a first-class environment in BIDI locales. This work will include
both improvemed access to native BIDI support and the better handling of
dynamic, complex expressions within Eclipse. [SWT, Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252645">252645</a>)</li>
<li><strong>Accessibility standards compliance.</strong>
We will work with the community to ensure that we have first-class, accessibility
support that is compliant with important standards. [SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252646">252646</a>)</li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Scalability and Performance</h3><p>Eclipse is being used consumed in an ever wider range of products, applications,
and development scenarios. We will identify and address performance and scalability
issues to provide a better experience both for users working in these areas in
particular, and for Eclipse users in general.
</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><strong>Performance testing infrastructure improvements.</strong>
We will improve our performance test infrastructure and result pages and ensure
that the test results are monitored on a daily basis. This will enable us to
more accurately and more readily identify any performance issues that might be
introduced during developement. [Rel. Eng.]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252649">252649</a>)</li>
<li><strong>Performance focus.</strong>
Although performance did not significantly degrade during the 3.4 release cycle,
we were unable to make the level of investment in performance improvements that
we had hoped for. In 3.5, we will dedicate significant effort to identifying and
ameliorating performance problems, both in typical Eclipse workflows and in more
extreme scenarios.
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252652">252652</a>)</li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Robustness</h3><p>As the basis for the entire Eclipse eco-system, the Eclipse SDK must be robust,
flexible and secure. This work will address those issues by providing API for
missing or currently internal functionality, and focusing on the issues that
effect the stability of the platform.
</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><strong>Provide API for missing/internal features.</strong>
We will identify areas where applications built on Eclipse currently must
invoke internal functionality in order to provide good integration with the SDK.
We will address these cases by creating proper, API-quality equivalents or
otherwise removing the dependencies on internals. [All]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252655">252655</a>) </li>
<li><strong>API Tools test suite and infrastructure</strong>
We will build a comprehensive regression test suite for our API tools, as well
as a performance test suite, and enhance analysis to avoid false positives, allow
special privileges between x-friend bundles, and detect when new API is used in
a prerequisite bundle that requires a version range adjustment. We will also
investigate architectural changes to support binary or source analysis and
performance improvements. [PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252658">252658</a>) </li>
<li><strong>API Tools enhancements</strong>
We will enhance the capabilities of our API tools. Potential work areas include
validating system library references based on a bundle&#8217;s required execution
environment; analyzing extension points for compatibility and considering extension
point modifications in bundle version validation; implementing API comparison
utilities that can be used to create reports in an automated build or presented
as a structural compare in the workbench; and providing tooling for package version
definition and validation. [PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252660">252660</a>) </li>
<li><strong>Compare editor improvements.</strong>
We will address some of the limitations of the current compare editor framework.
Possible work areas include: pluggable compare viewers/tools, automatic updating
of differences, better presentation for changes, support for auto-merge, ability
to hide outgoing annotations, better handling of hunks, and more
features from standard editors within compare editors.[All]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252662">252662</a>) </li>
<li><strong>Build process improvements.</strong>
The Eclipse build process is currently complex and brittle, impacting our
ability to deliver stable builds on a reliable schedule. We will make
improvements to the build process to make it more robust and reproducible.[Rel. Eng., PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252664">252664</a>) </li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Consumability</h3><p>This work will make it easier for users to get Eclipse, install it on their systems,
and configure it for their use. It also covers work related to error handling and reporting
mechanisms, and a number of enhancements to the Debug and PDE tools.</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><strong>User-assistance improvements.</strong>
We will provide a number of often asked for improvements to our help support,
such as filtering of the navigation tree based on Criteria, grouping of search
results based on Criteria, quick search from the navigation tree
(similar to quick print), better accessibility, and more control over the
presentation. [UA]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252661">252661</a>) </li>
<li><strong>Team sharable working sets.</strong>
The usefulness of working sets is limited by the fact they are not team
sharable. We will provide support for sharing working set information
between team members.[Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252663">252663</a>) </li>
<li><strong>Extensible execution environments.</strong>
Currently, the set of system library profile definitions supported by Equinox
is static (for example, J2SE-1.4, J2SE-1.5, etc.). We will respond to new
support being added by Equinox for an extensible set of system library profiles.
Default compiler options will be associated with each profile for creating new
Java and Plug-in projects. <em>(Note that completing this work will require
investment from the Equinox Project, in addition to the work here.)</em> [JDT, PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252665">252665</a>) </li>
<li><strong>PDE Build and Export enhancements.</strong>
We will support export and install of workspace bundles into the running host;
enhance product definition with start levels and license information and support
creation from OSGi launch configurations; honor the dropins folder when building
and resolving plug-in and feature dependencies; support parallel compilation of
bundles, incremental building, features with cyclic dependencies, exporting existing
class files from the workspace, and exporting individual source bundles. We will
leverage p2 function for fetch, publish and packaging build phases. [PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252666">252666</a>) </li>
<li><strong>Declarative Services Tooling.</strong>
We will provide tooling for authoring service component definitions. [PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252668">252668</a>) </li>
<li><strong>Debug User Interface Enhancements.</strong>
Investigate enhancements to streamline workflow and reduce clutter in the memory
view. Experiment with support for debugging without the debug view such as a
lightweight mechanism for switching and displaying the active debug context and
a top-level toolbar for debug actions (step, etc.). Investigate enhancements for
multi-context debugging such as creating multiple sets of debug views (variables,
registers, etc.), each dedicated to a single context. [Debug, UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252669">252669</a>) </li>
<li><strong>PDE Performance and Target Management.</strong>
Investigate performance improvements in plug-in XML and bundle manifest validation,
state maintenance, and plug-in launch configuration tabs. Enhance target platform
management and launching by leveraging p2&#8217;s provisioning infrastructure. Investigate
support for multiple target platforms in a workspace, switching between them, and
sharing target platforms with a team. [PDE]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252670">252670</a>) </li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Future</h3><p>Eclipse is well-established as the cross-platform IDE of choice, but it has become
much more than that. The extensive and diverse range of applications that are being
built on the Eclipse code base, and the constantly changing capabilities of the
underlying systems on which it runs, are driving us to push the limits of our
technology in almost every dimension. This work area continues our, multi-year
focus on innovation, to ensure that the Eclipse SDK continues to be a vibrant,
powerful, dynamic basis for our community's use.</p><p>Although some of the items under this theme will be delivered as part of the
Eclipse SDK R3.5, many represent ongoing work in the Eclipse 4.0 ("e4")
incubator, which is implementing the next major version of the Eclipse SDK.
See the <a href="http://wiki.eclipse.org/E4">e4 wiki</a> for more info.</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><strong>Flexible resources</strong>
The Resource architecture that Eclipse uses has been criticized for being
overly Java-centric and constraining for some use cases. We will
generalize the Resource layer (and related areas, such as EFS) to better
address these uses. [Workspace, Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252647">252647</a>)</li>
<li><strong>Support declarative definition of user-interfaces.</strong>
We will work with the community to identify and provide access to a best-of-breed
declarative mechanism for defining widget-based user-interfaces in Eclipse. [Platform UI, SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252648">252648</a>)</li>
<li><strong>Model-based workbench.</strong>
The functionality of the Eclipse Workbench and IDE have grown significantly
since they were created. In some cases, older capabilities have been superceded
by newer ones or have been proven to be unwieldy or otherwise unsatisfying.
We will create a new model of the underlying structure of the Eclipse UI, which
will make development simpler, but more flexible and dynamic. [Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id= 252650"> 252650</a>) </li>
<li><strong>Skinnable UI</strong>
We will enable developers to have greater control over the Eclipse UI,
making it simple to customize the appearance of Eclipse-based applications
using industry standard mechanisms such as CSS. [Platform UI, SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id= 252653"> 252653</a>) </li>
<li><strong>Investigate scripting languages for Eclipse programmability.</strong>
We will investigate the use of scripting languages such as JavaScript, Ruby, etc.,
in Eclipse development. Since this capability will require function from the
model-based workbench, as well as support from the Equinox project, and
will potentially impact many other areas, only the initial investigation
is planned during the R3.5 cycle. [All]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252654">252654</a>)</li>
<li><strong>Support advanced animation API in SWT.</strong>
A prototype API was developed during the R3.3 cycle that was implemented
on top of several desktop and web UI technologies. This work needs to be
completed. [SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252656">252656</a>)</li>
<li><strong>Support running SWT in a browser.</strong>
The RAP project has shown that it is possible to achieve good performance
and function for server-side, widget-based web applications. Investigations
have also been made into client-side technologies. Based on these efforts,
we will provide first-class support for the ability to run SWT applications
in web browsers. [SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252659">252659</a>)</li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><p><a href="#toc">Table of Contents</a></p><h2><a name="appendix">Appendix Execution Environment by Bundle</a></h2><p>In the table below, the "3.5 minimum execution environment"
column indicates the minimum Java class library requirements of each bundle
for the 3.5 release, where the value is one of:</p><table border="0" width="90%">
<tr>
<td align="center"><b>Entry</b></td>
<td align="left"><b>Meaning</b></td>
</tr>
<tr>
<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 for framework
implementations. See the OSGi specification for more details.</td>
</tr>
<tr>
<td width="9%"><div align="center"><strong>M1.1</strong></div></td>
<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><div align="center"><strong>F1.0</strong></div></td>
<td>J2ME Foundation 1.0 - indicates that the bundle 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.</td>
</tr>
<tr>
<td><div align="center"><strong>F1.1</strong></div></td>
<td>J2ME Foundation 1.1 - indicates that the bundle 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.</td>
</tr>
<tr>
<td><div align="center"><strong>1.2</strong></div></td>
<td>J2SE 1.2 - indicates that the bundle can only be run on JSE 1.2 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.3</strong></div></td>
<td>J2SE 1.3 - indicates that the bundle can only be run on JSE 1.3 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.4</strong></div></td>
<td>J2SE 1.4 - indicates that the bundle can only be run on JSE 1.4 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.4/1.5</strong></div></td>
<td>Indicates that the bundle can run on JSE 1.4 or greater, but provides
enhanced functionality when run on J2SE 5.0.</td>
</tr>
<tr>
<td><div align="center"><strong>1.5</strong></div></td>
<td>J2SE 5.0 - indicates that the bundle can only be run on JSE 5.0 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.6</strong></div></td>
<td>J2SE 6.0 - indicates that the bundle can only be run on JSE 6.0 or
greater.</td>
</tr>
<tr>
<td align="center"><b>n/a</b></td>
<td>Unknown at the time of this revision.</td>
</tr>
</table><p><b>Table of minimum execution environments by bundle.</b> (See also the
<a href="http://www.eclipse.org/projects/project-plan.php?projectid=rt.equinox#appendix">Equinox Project plan</a>
for the execution environment requirements of bundles contributed via that project.)</p><table border="1">
<tr>
<td width="290"><strong>Bundle</strong></td>
<td width="60"><div align="center"><p align="center"><b>3.5<br/>minimum<br/>execution<br/>environment</b></p></div></td>
</tr>
<tr>
<td>com.ibm.icu</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>com.jcraft.jsch</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.apache.lucene.analysis</td>
<td><div align="center">not specified</div></td>
</tr>
<tr>
<td>org.apache.lucene</td>
<td><div align="center">not specified</div></td>
</tr>
<tr>
<td>org.eclipse.ant.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ant.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.compare</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.boot</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.commands</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.contenttype</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.databinding.beans</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.databinding</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.core.expressions</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.filebuffers</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.filesystem</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.jobs</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.net</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.resources.compatibility</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.resources</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.core.runtime.compatibility.auth</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.runtime.compatibility.registry</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.runtime.compatibility</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.runtime</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.core.variables</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.cvs</td>
<td><div align="center">not specified</div></td>
</tr>
<tr>
<td>org.eclipse.debug.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.debug.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.help.appserver</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.help.base</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.help.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.help.webapp</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.help</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.apt.core</td>
<td><div align="center">1.5</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.apt.pluggable.core</td>
<td><div align="center">1.6</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.apt.ui</td>
<td><div align="center">1.5</div></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.manipulation</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.debug.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.debug</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.junit.runtime</td>
<td><div align="center">1.3</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.junit4.runtime</td>
<td><div align="center">1.5</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.junit</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.launching</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jdt</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jface.databinding</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.jface.text</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.jface</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<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>
</tr>
<tr>
<td>org.eclipse.ltk.core.refactoring</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ltk.ui.refactoring</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.api.tools.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.api.tools</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.build</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.junit.runtime</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.p2.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.runtime</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.ui.templates</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.pde</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.platform</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.rcp</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.sdk</td>
<td><div align="center">not specified</div></td>
</tr>
<tr>
<td>org.eclipse.search</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.swt</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.team.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.team.cvs.core</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.team.cvs.ssh2</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.team.cvs.ssh</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.team.cvs.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.team.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.text</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.browser</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.cheatsheets</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.console</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.editors</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.externaltools</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.forms</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.ide.application</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.ide</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.intro.universal</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.intro</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.navigator.resources</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.navigator</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.net</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.ui.presentations.r21</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.views.log</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.views.properties.tabbed</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.ui.views</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.win32</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.workbench.compatibility</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.workbench.texteditor</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.ui.workbench</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.ui</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.update.configurator</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.update.core</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.update.scheduler</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.update.ui</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.junit4</td>
<td><div align="center">1.5</div></td>
</tr>
<tr>
<td>org.junit</td>
<td><div align="center">1.3</div></td>
</tr>
<tr>
<td>org.objectweb.asm</td>
<td><div align="center">1.3</div></td>
</tr>
</table><p><a href="#toc">Table of Contents</a></p></div>
</div>
</div>
<div style="visibility: hidden; float: right; text-align: right"><a href="?projectid=eclipse&raw=1">view raw xml of project plan</a><br>
<a href="http://www.eclipse.org/projects/dev_process/project-status-infrastructure.php">from project meta-data key "projectplanurl"</a></div>
</div> <!-- midcolumn -->
</div> <!-- maincontent -->
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
var pageTracker = _gat._getTracker("UA-910670-2");
pageTracker._initData();
pageTracker._trackPageview();
</script></div><div id="footer">
<ul id="footernav">
<li class="first"><a href="http://www.eclipse.org/">Home</a></li>
<li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
<li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a><a href="http://www.eclipse.org/org/press-release/20081112_termsofuse.php"><img src="http://www.eclipse.org/images/updated.png" align="absmiddle" /></a></li>
</ul>
<p>Copyright &copy; 2008 The Eclipse Foundation. All Rights Reserved</p>
</div></body></html>