Notice: This Wiki is now read only and edits are no longer 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) |
|||
| Line 7: | Line 7: | ||
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal]) | Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics 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 === | ||
| + | * {{bug|106676}}: [pde viz] Graduate | ||
| + | |||
| + | == 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 | ||
| + | ** {{bug|283731}} | ||
| + | * 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 == | == 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). | |
| + | * Consider scans taylored to show API use based on frequency of use - i.e. what APIs internals are used most heavily. | ||
* Performance improvements | * Performance improvements | ||
| − | |||
| − | |||
== Build == | == Build == | ||
| Line 50: | Line 74: | ||
* {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini | * {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini | ||
| − | |||
| − | + | = 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 |
| − | + | ||
| − | + | ||
[[Category:PDE]] | [[Category:PDE]] | ||
Revision as of 12:41, 16 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
- bug 106676: [pde viz] Graduate
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
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
Build
- bug 154083: Incremental Plug-in Build
- bug 106594: Make PDE fully workspace aware
- bug 222965: Use frameworkadmin to generate config.ini / eclipse.ini
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