Difference between revisions of "Equinox Planning - 3.3"

Revision as of 13:03, 4 December 2006

Equinox Planning - 3.3

General Planning Notes

Note: This is just a random collection of notes and thoughts and does not reflect the actual committed plan items for the Equinox team.

• Declarative Services
  • Implementation
  • Tooling

• Update Manager
  • The update manager code ownership is migrating from Toronto to Ottawa. We need to keep on top of bug reports and current problems to ensure that nothing slips by for 3.2.1.
  • We need to investigate refactoring the JarProcessor code. It was put into the Update bundles at the end of the 3.2 cycle but is more generally useful.
  • JarProcessor - might be some more work here w.r.t. JAR signing and nested JARs

• Provisioning
  • Prototype
  • Investigate MEG
  • How to deliver Eclipse?
    • Small installer download?
    • Dynamic web content that builds zip?

• PDE/Build
  • Continue investigation into inter-operability with Maven
  • Incremental building

• Component Model
  • The programming model.
  • Investigate Spring, DS, etc.
  • We want to get people off the Platform class.
  • Need to have something easy for people to use when they migrate their code.

• OSGi Framework (refactor/etc)

• Investigation into Security
  • Login authentication
  • Securing the code base (Java 2 security)

• Launching
  • Launching the VM in-process
  • Splash Screen
  • fast workspace switching (currently we don't have any lifecycle events for location areas)

• Preferences
  • API fixes
  • use everywhere - get people to adapt and get off the old JFace and Runtime prefs code
  • should we create more scopes?
  • Work on an RFC for scopes as they seem generally useful. (particularly for searching)
  • use common storage solution (described below)

• Version Tools
  • We have started working on some version verification tools to help people cope with the new plug-in (and feature) version number story.
  • Super cool goal is to complete these tools and have them integrated into the SDK.
  • Cool goal is to have them available as either part of the Core Tools or PDE Tools.

• Storage Service
  • Many different components have to serialize and they all roll their own storage solution whether it be using Properties files, ObjectOutputStreams, or another format.
  • We should investigate a common storage service that multiple components can leverage.

• Service Registry
  • Lazy Tracking
  • Scalability issues for event dispatching and registry impl

• Refactor Test Suites
  • We used to have one test plug-in for each plug-in in the SDK.
  • Now that we have refactored the runtime we should also refactor the test suites to match the new bundle structure.

Milestone Plans

Eclipse 3.3 M4 - Friday Dec. 15, 2006

New Lancher Work

API Tooling

• Initial work on the engine for collection and comparison of APIs
• Initial work on the tool for collection of references to APIs/non-APIs in other projects
• Find a home in one of the incubators for this work

The Supplement Bundle

Generally speaking, the org.eclipse.supplement bundle is a collection of classes that are required for the registry to run outside of OSGi. It also should contain the classes necessary to run the registry on another framework.

Currently this bundle lives in a separate project in the Eclipse repository so therefore the classes are copied from the org.eclipse.osgi bundle and live in 2 locations. We need to make it easier to maintain the code whether it be by combining the projects into one so there is only one code base, or by some other means.

The goal for 3.3 M4 is to have the supplement bundle work completed. The code should be maintained from a single location be able to run both with and without OSGi present.

Orbit

Eclipse 3.3 M5 - Date TBD

Eclipse 3.3 M6 - Date TBD