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 40: | Line 40: | ||
** Follow code graduation review process [[Image:Ok green.gif|done]] | ** Follow code graduation review process [[Image:Ok green.gif|done]] | ||
** Create new plug-ins in the SDK with committers from the incubation project[[Image:progress.gif|in progress]] | ** Create new plug-ins in the SDK with committers from the incubation project[[Image:progress.gif|in progress]] | ||
− | ** Rename packages such that all code is 'internal' - i.e. no published API planned for first release[[Image: | + | ** Rename packages such that all code is 'internal' - i.e. no published API planned for first release[[Image:Ok green.gif|done]] |
* Add API description metadata to automated builds | * Add API description metadata to automated builds | ||
** Enhance automated builds to generate .api_description files to be included with each binary bundle such that a build can be used as an API profile [[Image:Ok green.gif|done]] | ** Enhance automated builds to generate .api_description files to be included with each binary bundle such that a build can be used as an API profile [[Image:Ok green.gif|done]] |
Revision as of 13:00, 4 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
- Configure reference extractor to extract only specific reference kinds
- Command line tool to create XML file for illegal extending, implementing, and instantiating [move to priority 2]
- Preference page to select API usage baseline [not needed - same as target platform]
- Create markers in the workspace for illegal API use based on API usage baseline
Priority Two
- Binary compatibility
- API Usage
- Implementation of plug-in project API component
- Updates API description and class files dynamically with edits in the workspace
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.