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 23: | Line 23: | ||
<h4>Priority Two</h4> | <h4>Priority Two</h4> | ||
− | * Binary compatibility | + | * Binary compatibility [[Image:progress.gif|in progress]] |
+ | ** Provide XSLT file to create HTML report from XML output | ||
+ | ** Batch report and IDE markers for missing @since tags and incorrect plug-in version numbers [[Image:Ok green.gif|done]] | ||
+ | ** Incremental binary compatibility checking in IDE [[Image:Ok green.gif|done]] | ||
+ | * API Usage [[Image:progress.gif|in progress]] | ||
** Provide XSLT file to create HTML report from XML output | ** Provide XSLT file to create HTML report from XML output | ||
− | + | ** Incremental API usage scans in IDE (for illegal extending, implementing, and instantiating) [[Image:Ok green.gif|done]] | |
− | + | * Implementation of plug-in project API component [[Image:Ok green.gif|done]] | |
− | + | ** Updates API description and class files dynamically with edits in the workspace [[Image:progress.gif|in progress]] | |
− | + | ||
− | ** Incremental API usage scans in IDE (for illegal extending, implementing, and instantiating) [[Image: | + | |
− | * Implementation of plug-in project API component [[Image: | + | |
− | ** Updates API description and class files dynamically with edits in the workspace | + | |
== 3.4 Milestone 5 (Friday February 8, 2008 ) == | == 3.4 Milestone 5 (Friday February 8, 2008 ) == |
Revision as of 15:18, 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
- 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
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.