Skip to main content

Project Plan For Eclipse Project, version Galileo

Introduction

Last revised 16:00 ET May 13, 2009 ((new) marks interesting changes since the previous draft of April 3, 2009)

Please send comments about this plan to the eclipse-dev@eclipse.org developer mailing list.

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.

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.

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.

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.

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.

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.

The current status of each plan item is noted:

  • Committed plan item - A committed plan item is one that we have decided to address for the release.
  • Proposed 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.
  • Deferred 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.

Release Deliverables

The release deliverables have the same form as previous releases, namely:

  • Source code release for all Eclipse Project deliverables, available as versions tagged "R3_5" in the Eclipse Project CVS repository.
  • Eclipse SDK (runtime binary and SDK for Equinox[*], Platform, JDT, and PDE) (downloadable).
  • Eclipse Platform (runtime binary and SDK for the Equinox[*] and Platform only) (downloadable).
  • Eclipse RCP (runtime binary and SDK for the Rich Client Platform) (downloadable).
  • Eclipse JDT (runtime binary and SDK for the Java Development Tools) (downloadable).
  • Eclipse PDE (runtime binary and SDK for the Plug-in Development Environment) (downloadable).
  • Eclipse SDK Examples (downloadable).
  • SWT distribution (downloadable).

* The Equinox Project is part of the top level RT Project. A significant portion of the Equinox deliverables are consumed and redistributed as part of the Eclipse Project's SDK, Platform, and RCP deliverables.

Table of Contents

Release Milestones

Release milestones will be occurring at roughly 6 week intervals, and will be aligned with the Galileo Simultaneous Release train.

M108/08/2008
3.5M1
M209/19/2008
3.5M2
M310/31/2008
3.5M3
M412/12/2008
3.5M4
M501/30/2009
3.5M5
M603/13/2009
3.5M6 (API Freeze)
M705/01/2009
3.5M7 (Feature Freeze)

Individual, milestone level plans for the components that make up the Eclipse Project can be found on the Eclipse Project Galileo Plan page on the Eclipse wiki.

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.

Dates for builds after M7 can be found in the Eclipse Galileo end-game plan

Table of Contents

Target Environments

In order to remain current, each Eclipse Project release targets reasonably current operating environments.

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

In general, the 3.5 release of the Eclipse Project is developed on a mix of Java 1.4, Java 5 and Java 6 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.

Appendix 1 contains a table that indicates the class library level required for each bundle.

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 reference platforms. 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.

Eclipse 3.5 is tested and validated on the following reference platforms (this list is updated over the course of the release cycle):

Reference Platforms
Microsoft Windows Vista, x86-32, Win32 running (any of):
  • Sun Java Standard Edition 5 Update 14 for Microsoft Windows
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
  • BEA JRockit 27.4.0, for Microsoft Windows
Microsoft Windows XP, x86-32, Win32 running (any of):
  • Sun Java Standard Edition 6 Update 3 for Microsoft Windows
  • Sun Java Standard Edition 5 Update 14 for Microsoft Windows
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
  • BEA JRockit 27.4.0, for Microsoft Windows
  • Sun Java Standard Edition 1.4.2_16 for Microsoft Windows
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition 1.4.2 SR10
Red Hat Enterprise Linux 5.0, x86-32, GTK running (any of):
  • Sun Java Standard Edition 6 Update 3 for Linux x86
  • Sun Java Standard Edition 5 Update 14 for Linux x86
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b
  • BEA JRockit 27.4.0, for Linux x86
  • Sun Java Standard Edition 1.4.2_16 for Linux x86
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 1.4.2 SR10
SUSE Linux Enterprise Server 10, x86-32, GTK running (any of):
  • Sun Java Standard Edition 5 Update 14 for Linux x86
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b
(new) SUSE Linux Enterprise Server 10, x86-64, GTK running (any of):
  • Sun Java Standard Edition 5 Update 14 for Linux x86-64
  • IBM 64-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b
Microsoft Windows Vista, x86-64, Win32 running (any of):
  • Sun Java Standard Edition 5 Update 14 for Microsoft Windows (AMD64/EM64T)
  • IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
Microsoft Windows XP Professional x64 Edition, x86-64, Win32 running (any of):
  • Sun Java Standard Edition 5 Update 14 for Microsoft Windows (AMD64/EM64T)
  • IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
Red Hat Enterprise Linux 4.0 update 2, x86-64, GTK running:
  • Sun Java Standard Edition 5 Update 14 for Linux x86-64
  • (new) IBM 64-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b
Sun Solaris 10, SPARC, GTK running:
  • Sun Java Standard Edition 5 Update 14 for Solaris SPARC
(new) Sun Solaris 10, x86, GTK running:
  • Sun Java Standard Edition 5 Update 14 for Solaris
HP-UX 11i v2, ia64, Motif 2.1, GTK running:
  • HP-UX Java Standard Edition 5 Update 7 for Itanium
IBM AIX 5.3, Power, Motif 2.1 running:
  • IBM 32-bit SDK, Java 2 Technology Edition 5.0, SR6b
Red Hat Enterprise Linux 5.0, Power, GTK running:
  • IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b
SUSE Linux Enterprise Server 10, Power, GTK running:
  • IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b
Apple Mac OS X 10.5, Universal, Carbon running:
  • Apple Java for Mac OS X 10.5, Update 1
Apple Mac OS X 10.5, Universal 32-bit, Cocoa running:
  • Apple Java for Mac OS X 10.5, Update 1
(new) Apple Mac OS X 10.5, Universal 64-bit, Cocoa running:
  • Apple Java for Mac OS X 10.5, Update 1

As stated above, 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.

Internationalization

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.

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.

The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, on Windows XP and 2000, Linux/GTK and the Macintosh.

German and Japanese locales are tested.

Table of Contents

Compatibility with Previous Releases

Compatibility of Release 3.5 with 3.4

Eclipse 3.5 will be compatible with Eclipse 3.4 (and all earlier 3.x versions).

API Contract Compatibility: Eclipse SDK 3.5 will be upwards contract-compatible with Eclipse SDK 3.4 except in those areas noted in the Eclipse 3.5 Plug-in Migration Guide . 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 Evolving Java-based APIs for a discussion of the kinds of API changes that maintain contract compatibility.

Binary (plug-in) Compatibility: Eclipse SDK 3.5 will be upwards binary-compatible with Eclipse SDK 3.4 except in those areas noted in the Eclipse 3.5 Plug-in Migration Guide . 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 Evolving Java-based APIs for a discussion of the kinds of API changes that maintain binary compatibility.

Source Compatibility: Eclipse SDK 3.5 will be upwards source-compatible with Eclipse SDK 3.4 except in the areas noted in the Eclipse 3.5 Plug-in Migration Guide . 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.

Workspace Compatibility: Eclipse SDK 3.5 will be upwards workspace-compatible with earlier 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 on an earlier version of Eclipse. Visible metadata files created (or overwritten) by Eclipse 3.5 will generally be unusable with earlier versions of Eclipse.

Non-compliant usage of API's: 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 How to Use the Eclipse API for information about how to write compliant plug-ins.

Table of Contents

Themes and Priorities

The plan items listed below were defined according to contributor requirements and the Eclipse Themes and Priorities 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.

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.

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.

The current status of each plan item is noted:

  • Committed 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.
  • Proposed 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.
  • Deferred 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.

Platforms

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.

  • Committed
    • Support Cocoa on Mac OS X. Apple GUI development is moving from Carbon to Cocoa. We will support the Eclipse SDK running on Mac OS Cocoa (including 64-bit Java 6), to ensure that Eclipse continues to be a first-class application delivery and development platform on the Mac. (Note that completing this work will require investment from the Equinox Project, in addition to the work here.) [SWT, Platform UI] (252644)
    • BIDI improvements. 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] (252645)
  • Proposed

    None at this time.

  • Deferred
    • ((new) deferred) Accessibility standards compliance. We will work with the community to ensure that we have first-class, accessibility support that is compliant with important standards. [SWT] (252646)

Scalability and Performance

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.

  • Committed
    • Performance testing infrastructure improvements. 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.] (252649)
    • ((new) committed) Performance focus. 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. (252652)
  • Proposed

    None at this time.

  • Deferred

    None at this time.

Robustness

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.

  • Committed
    • API Tools test suite and infrastructure 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] (252658)
    • Compare editor improvements. 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] (252662)
    • Build process improvements. 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] (252664)
    • ((new) committed) API Tools enhancements We will enhance the capabilities of our API tools. Potential work areas include validating system library references based on a bundle’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] (252660)
  • Proposed

    None at this time.

  • Deferred
    • ((new) deferred) Provide API for missing/internal features. 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] (252655)

Consumability

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.

  • Committed
    • User-assistance improvements. 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] (252661)
    • Extensible execution environments. 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. (Note that completing this work will require investment from the Equinox Project, in addition to the work here.) [JDT, PDE] (252665)
    • PDE Build and Export enhancements. 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] (252666)
    • Declarative Services Tooling. We will provide tooling for authoring service component definitions. [PDE] (252668)
    • ((new) committed) Debug User Interface Enhancements. 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] (252669)
    • ((new) committed) PDE Performance and Target Management. 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’s provisioning infrastructure. Investigate support for multiple target platforms in a workspace, switching between them, and sharing target platforms with a team. [PDE] (252670)
  • Proposed

    None at this time.

  • Deferred
    • ((new) deferred) Team sharable working sets. 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] (252663)

Future

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.

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 e4 wiki for more info.

Plan items from the future theme have been moved to the e4 project 0.9 release plan.

Table of Contents

Appendix Execution Environment by Bundle

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:

Entry Meaning
F1.0
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.
F1.1
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.
1.3
J2SE 1.3 - indicates that the bundle can only be run on JSE 1.3 or greater.
1.4
J2SE 1.4 - indicates that the bundle can only be run on JSE 1.4 or greater.
1.5
Java SE 5 - indicates that the bundle can only be run on Java SE 5 or greater.
1.6
Java SE 6 - indicates that the bundle can only be run on Java SE 6 or greater.
n/a Unknown at the time of this revision.

Table of minimum execution environments by bundle. (See also the Equinox Project plan for the execution environment requirements of bundles contributed via that project.)

Bundle

3.5
minimum
execution
environment

com.ibm.icu
F1.0
com.jcraft.jsch
1.4
org.apache.ant
J2SE-1.2
org.apache.lucene
not specified
org.apache.lucene.analysis
not specified
org.eclipse.ant.core
1.4
org.eclipse.ant.ui
1.4
org.eclipse.compare
1.4
org.eclipse.compare.core
1.4
org.eclipse.compare.win32
1.4
org.eclipse.core.boot
F1.0
org.eclipse.core.commands
F1.0
org.eclipse.core.contenttype
F1.0
org.eclipse.core.databinding
F1.1
org.eclipse.core.databinding.beans
1.4
(new)org.eclipse.core.databinding.observable
F1.1
(new)org.eclipse.core.databinding.property
F1.1
org.eclipse.core.expressions
F1.0
org.eclipse.core.filebuffers
1.4
org.eclipse.core.filesystem
1.4
org.eclipse.core.jobs
F1.0
org.eclipse.core.net
F1.1
org.eclipse.core.resources
1.4
org.eclipse.core.resources.compatibility
1.4
org.eclipse.core.runtime
F1.0
org.eclipse.core.runtime.compatibility
F1.0
org.eclipse.core.runtime.compatibility.auth
F1.0
org.eclipse.core.runtime.compatibility.registry
F1.0
org.eclipse.core.variables
1.4
org.eclipse.cvs
not specified
org.eclipse.debug.core
1.4
org.eclipse.debug.ui
1.4
org.eclipse.help
F1.0
org.eclipse.help.appserver
F1.0
org.eclipse.help.base
1.4
org.eclipse.help.ui
1.4
org.eclipse.help.webapp
1.4
org.eclipse.jdt
not specified
org.eclipse.jdt.apt.core
1.5
org.eclipse.jdt.apt.pluggable.core
1.6
org.eclipse.jdt.apt.ui
1.5
org.eclipse.jdt.compiler.apt
1.6
org.eclipse.jdt.compiler.tool
1.6
org.eclipse.jdt.core
1.4
org.eclipse.jdt.core.manipulation
1.4
org.eclipse.jdt.debug
1.4
org.eclipse.jdt.debug.ui
1.4
org.eclipse.jdt.doc.isv
not specified
org.eclipse.jdt.doc.user
not specified
org.eclipse.jdt.junit
1.4
org.eclipse.jdt.junit.runtime
1.3
org.eclipse.jdt.junit4.runtime
1.5
org.eclipse.jdt.launching
1.4
org.eclipse.jdt.ui
1.4
org.eclipse.jface
F1.1
org.eclipse.jface.databinding
F1.0
org.eclipse.jface.text
1.4
org.eclipse.jsch.core
1.4
org.eclipse.jsch.ui
1.4
org.eclipse.ltk.core.refactoring
1.4
org.eclipse.ltk.ui.refactoring
1.4
org.eclipse.pde
1.4
org.eclipse.pde.api.tools
1.4
org.eclipse.pde.api.tools.ui
1.4
org.eclipse.pde.build
1.4
org.eclipse.pde.core
1.4
org.eclipse.pde.doc.user
not specified
org.eclipse.pde.ds.core
1.4
org.eclipse.pde.ds.ui
1.4
org.eclipse.pde.junit.runtime
1.4
org.eclipse.pde.runtime
1.4
org.eclipse.pde.ua.core
1.4
org.eclipse.pde.ua.ui
1.4
org.eclipse.pde.ui
1.4
org.eclipse.pde.ui.templates
1.4
org.eclipse.platform
F1.0
org.eclipse.platform.doc.isv
not specified
org.eclipse.platform.doc.user
not specified
org.eclipse.rcp
not specified
org.eclipse.sdk
not specified
org.eclipse.search
1.4
org.eclipse.swt
F1.0
org.eclipse.team.core
1.4
org.eclipse.team.cvs.core
1.4
org.eclipse.team.cvs.ssh
1.4
org.eclipse.team.cvs.ssh2
1.4
org.eclipse.team.cvs.ui
1.4
org.eclipse.team.ui
1.4
org.eclipse.text
1.4
org.eclipse.ui
F1.0
org.eclipse.ui.browser
1.4
org.eclipse.ui.cheatsheets
1.4
org.eclipse.ui.console
1.4
org.eclipse.ui.editors
1.4
org.eclipse.ui.externaltools
1.4
org.eclipse.ui.forms
1.4
org.eclipse.ui.ide
1.4
org.eclipse.ui.ide.application
1.4
org.eclipse.ui.intro
1.4
org.eclipse.ui.intro.universal
1.4
org.eclipse.ui.navigator
1.4
org.eclipse.ui.navigator.resources
1.4
org.eclipse.ui.net
F1.1
org.eclipse.ui.presentations.r21
1.4
org.eclipse.ui.views
1.4
org.eclipse.ui.views.log
1.4
org.eclipse.ui.views.properties.tabbed
F1.0
org.eclipse.ui.win32
1.4
org.eclipse.ui.workbench
(new) F1.1
org.eclipse.ui.workbench.compatibility
1.4
org.eclipse.ui.workbench.texteditor
1.4
org.eclipse.update.configurator
F1.0
org.eclipse.update.core
F1.0
org.eclipse.update.core.win32
not specified
org.eclipse.update.scheduler
F1.0
org.eclipse.update.ui
F1.0
(new)org.hamcrest.core
1.5
org.junit
1.3
org.junit4
1.5
org.objectweb.asm
1.3

Table of Contents

Back to the top