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 "ApiTools Milestones"
Line 18: | Line 18: | ||
** Preference page to select API usage baseline [not needed - same as target platform] [[Image:Ok green.gif|done]] | ** Preference page to select API usage baseline [not needed - same as target platform] [[Image:Ok green.gif|done]] | ||
** Create markers in the workspace for illegal API use based on API usage baseline [[Image:Ok green.gif|done]] | ** Create markers in the workspace for illegal API use based on API usage baseline [[Image:Ok green.gif|done]] | ||
− | * Performance | + | * Performance [[Image:progress.gif|in progress]] |
− | ** Stress test incremental builder | + | ** Stress test incremental builder [[Image:progress.gif|in progress]] |
− | ** Profile incremental builder | + | ** Profile incremental builder [[Image:progress.gif|in progress]] |
** Stress test api usage and binary compatibility checking | ** Stress test api usage and binary compatibility checking | ||
− | ** Stress test workspace api component updating/creation | + | ** Stress test workspace api component updating/creation [[Image:progress.gif|in progress]] |
** Profile workspace component | ** Profile workspace component | ||
Revision as of 15:23, 8 February 2008
Contents
3.4 Milestone 4 (December 14th, 2007)
API tooling will reside in the incubator project. The plug-ins can be exported and dropped into an Eclipse SDK. Works items marked as Priority One are must haves, while Priority Two items are nice to have that may slide to the next milestone.
Priority One
- Finalize Javadoc tags and code comments
- Export API components from command line and IDE
- Binary compatibility
- API Usage
- Performance
Priority Two
3.4 Milestone 5 (Friday February 8, 2008 )
Priority One
- Graduate code to the Eclipse SDK
- Add API description metadata to automated builds
- Binary Compatibility
- Version Management
- API Problem Filtering
- Builder
- Java 5.0 Support
- Properly support reference extraction for Java 5.0 signatures
Priority Two
- API Searching
- Investigate and define API searching. Should it be similar to Java searching in the workspace (i.e. search a profile for use of a bundle, package, type, method, etc.), or something else? Will we need source in order to browse search results?
- Version Management
- Validate required bundle compatibility in terms of API use. When provided with several versions of a required bundle, determine the minimal compatible version. Help developers determine where required bundle version ranges are too restrictive.