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.
Difference between revisions of "PDE/Plan/3.6"
(→API Tools) |
(→API Tools) |
||
| Line 34: | Line 34: | ||
== API Tools == | == API Tools == | ||
| − | * API Use | + | * API Use Scans |
** Make it really easy to generate 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) | ** Output can be HTML report or search results in the IDE (with attached source) | ||
Revision as of 15:48, 8 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.
Contents
Schedule
Dates are listed in the Eclipse Platform Releng Calendar (view as iCal)
Scope
TODO
Priorities
- PDE becomes BDE: more bundle, less plug-in
- Revamp the PDE webpage to be more welcoming
- Add missing Incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects
- More tests to improve code coverage
- Get more committers
- One mailing list (ie., just pde-dev, get rid of pde-build-dev and pde-ui-dev)?
Platforms
- Eclipse: 3.6
- Target Platforms back to 3.0 supported
- Java: J2SE 1.4 or later required
- Operating Systems: all supported by Eclipse
Ramp Down
TODO
Projects
API Tools
- 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).
- Performance improvements
- bug 215073: [api tooling] Support for package versioning
- bug 255771: Report usage of non-available new code
Build
- bug 154083: Incremental Plug-in Build
- bug 106594: Make PDE fully workspace aware
- bug 222965: Use frameworkadmin to generate config.ini / eclipse.ini
UI
- bug 216037: [API] Way to modify MANIFEST files
- 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. As well, OSGi state could be associated with target definitions and leveraged for per-project target build paths.
- bug 169340: [API] [target] Expose a means to programmatically set and load a Target Platform
- bug 159072: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)
- bug 269573: [product] support more platforms in product files
- bug 260328: [product] add a way to specify properties
- bug 106676: [pde viz] Graduate
- bug 142422: [refactoring] update class references in dependent plugins
- bug 231099: [launching] Make launch config files more CVS-friendly
- bug 164188: Need tooling for access rules on vm packages
- bug 227055: [schema] allow for the definition of custom attribute types
- p2 publishing tooling (replace update site tooling)