Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDE/Plan/3.6"

< PDE‎ | Plan
(API Tools)
(UI Consumability / Search)
Line 86: Line 86:
  
 
* Provide current UI offering in core code. The current offering is available [http://www.eclipse.org/pde/pde-api-tools/internal_updates/ here].
 
* Provide current UI offering in core code. The current offering is available [http://www.eclipse.org/pde/pde-api-tools/internal_updates/ here].
* update the code to be in a wizard, not necessarily in the search dialog
+
* Update the code to be in a wizard, not necessarily in the search dialog
 
* Provide output to search view / API tooling view along with reports
 
* Provide output to search view / API tooling view along with reports
  

Revision as of 11:52, 20 July 2009

Note: This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.

Schedule

Dates are listed in the Eclipse Platform Releng Calendar (view as iCal)

Overall Goals

Improve PDE code quality

  • Better testing
  • Better milestone/release ramp down

More to come...

Work Items

PDE General

Bundles or Plug-ins

  • Rename PDE to Bundle Development Environment
  • Use of the word plug-in in UI

Improve PDE communications

  • Continued web page improvements
  • Use of wiki for meetings/planning
  • Combine mailing lists
    • Completed
  • Involve incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects
  • Integrate wiki based documentation

Graduate PDE Dependency Visualizer

PDE UI

Improve code quality

  • Write tests for core components
  • Improve code readability and javadoc of APIs
  • Consider code coverage in tests

Target Platform

  • Continue target platform definition enhancements.
  • Target platform/definition contents could be managed entirely with p2 profiles for improved performance and for proper persistence/restoration.
  • OSGi state could be associated with target definitions and leveraged for per-project target build paths.
  • Remove dependency on preferences
  • Improved APIs
    • bug 169340: [API] [target] Expose a means to programmatically set and load a Target Platform
  • Multiple target platforms
    • bug 159072: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)

API Tools

General

API Use Scans

  • Make it really easy to generate API use scans
  • Output can be HTML report or search results in the IDE (with attached source)
  • Compare API use scans to see summary of dependencies added/removed between successive scans
  • Analyze scans for potential breakage (internal dependencies) when moving to a new version of required components (for example WTP moving to a new version of the Eclipse SDK).
  • Consider scans taylored to show API use based on frequency of use - i.e. what APIs internals are used most heavily.
  • Performance improvements

UI Consumability / Search

  • Provide current UI offering in core code. The current offering is available here.
  • Update the code to be in a wizard, not necessarily in the search dialog
  • Provide output to search view / API tooling view along with reports

Internal Use Breakage Analysis

  • Provide tooling to inspect internal use and breakage (potential or otherwise)
  • Provide as user-run tooling and evaluate build-time tooling

Required Bundle Validation

  • Validate the bounds of required bundles based on the references from the bundle
  • Provide as user-run tooling and evaluate build-time performance

Package Version Support

  • Validate package versions wrt bundle versions / usage from required bundles
  • Provided as user-run tooling and evaluate build-time performance

Build

Platform Support

  • Eclipse: 3.6
  • Target Platforms back to 3.0 supported
  • Java: J2SE 1.4 or later required
  • Operating Systems: all supported by Eclipse

Back to the top