PDE/UI 3.5 Plan

PDE UI 3.5 Plan

Last revised: 2008/08/27

This plan is under continuous refinement. Please send comments about this plan to the pde-ui-dev@eclipse.org developer mailing list.

Overall Goals

This section lists the goals for Eclipse 3.5 for the PDE/UI component as listed on the Eclipse Project 3.5 Draft Plan.

[1] Performance. Monitor overall performance and memory consumption.

[2] Reliability. Fix critical bugs.

[3] Keep Eclipse vibrant and attractive. Investigate and implement enhancements such support for custom execution environments, p2 based target platform definitions and enhanced Equinox support.

Milestone M1 (2008-08-08)

General Items [2]

  • 3.4.1 maintenance work
  • Bug fixing
Milestone M2 (2008-09-19)

General Items [2]

  • 3.4.1 maintenance work
  • Bug fixing
  • Planning

Declarative Services Tooling [3]

  • Create an editor and additional tooling to handle service component definitions as defined in the OSGi specification [bug 242027]

Package Versioning Improvements [3]

  • Come up with a plan along with the Equinox team on how to handle package versions in Eclipse
  • Offer configurable settings to check for missing package versions on exported packages and offer potential quickfixes [bug 205198]
  • Offer configurable settings to check for missing package versions on imported packages and offer potential quickfixes [bug 205198]
Milestone M3 (2008-10-31)

Custom Execution Environments[3]

  • A joint effort between Equinox, JDT, and PDE. Equinox needs support for contributing system library profile definitions (such as J2SE-1.4, etc.). JDT needs support to associate compiler options with a system profile. PDE will set default compiler options for bundles based on the bundle's profile. Similarly, JDT will set the compiler options for a Java project. (Darin Wright, IBM) [bug 238802]

Usability/Workflow [3]

  • One click plug-in export and installation into development environment (Curtis Windatt, IBM)
    • Leverage p2 to export and install bundles into the running SDK for testing the latest code base [bug 222945]
  • Product definition enhancements
    • The ability to set start levels on a product [bug 240737]
    • The ability to set a validate a product [bug 247920]
    • The ability to set a license on a product [bug 241169]
    • The ability to create product definitions from OSGi launch configurations [bug 245782]
  • Eclipse-BundleShape
    • The ability to tool the Eclipse-BundleShape header [bug 217007]
  • Refactoring legacy PDE code base
    • Move PDE User Assistance tooling into a new set of plug-ins [bug 241145]

Performance [1]

  • Analyze PDE's plug-in XML builder/validation and create a performance test for it
  • Analyze PDE's OSGi state maintenance to see if can be shared with API tools
  • Optimize PDE's launch configuration dialog for performance [bug 229073]

Testing

Milestone M4 (2008-12-12)

Usability/Workflow [3]

  • Improve target platform management (Curtis Windatt, IBM)
    • Define a target platform based on an existing p2 installation of bundles
    • Support target platform definition by creating/modifying a p2 installation of bundles (download and install bundles into a target from update sites)
    • Support multiple target platform definitions in the workspace, with one active target platform that workspace projects are built against (preference page with check box for active target)
    • Support per-project target platforms
    • Support versions in target definition files
    • Investigate sharing target platform definitions with a development team
    • Source code should be installed in/part of a target platform (source bundles) rather than a global setting
    • Support target management for non-p2 installs (update manager) in a similar fashion
  • Polish one-click export and install feature [bug 249849] (Curtis Windatt, IBM)
    • Improve UI look and feel (enablement, tab interdependency, error reporting)
    • Improve metadata repository management (space issues, naming)
    • Improve robustness

Testing

Milestone M5 (2009-01-30) - Major/Big Features Done

Usability/Workflow [3]

  • [>M6] Support to export source bundles from the SDK
  • Target platform enhancements
    • Create a new target platform model implementation and operation for setting the active target platform
    • Support target definitions stored locally with workspace metadata and in the workspace as managed resources
    • Migrate the existing target platform editor to work on the new model
    • Support multiple target platform definitions in the workspace, with one active target platform that workspace projects are built against (preference page with check box for active target)

Testing

Milestone M6 (2009-03-13) - API Freeze

Usability/Workflow [3]

  • [>from M5] Support to export source bundles from the SDK
  • Analyze dependencies on old Update Manager. If possible make PDE optionally dependant on update bundles, such that we could operate without update.

Performance

Polish

  • Continued target platform definition enhancements
    • Support for optional bundles in target definitions for backwards compatibility (infrastructure only, not UI enabled)
    • Enhanced target definition resolution to provide information on missing bundles, version matching problems, and progress reporting
    • Enhanced target platform creation/edit wizard/dialogs to improve usability
    • Enhance support to append .ini VM arguments to target definitions and launch configurations
    • Documentation for new target definition UI and editor

Testing

Milestone M7 (2009-05-01) - Feature Freeze, Focus on Performance and Polish

Performance

Polish

Testing

Legend
item is under development. item is under investigation.
item is finished. ( ) item is time permitted.
[xyz] item is deferred (>) from xyz or continues in xyz. new