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 "XSL Tools/API Tooling"
(Added to "how to" category) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 13: | Line 13: | ||
The name should be WTP 3.0. | The name should be WTP 3.0. | ||
| − | [[Category:XSL Tools]] | + | =Adding PDE API Tooling to a Plugin= |
| + | |||
| + | #Select a project plugin, and right click. | ||
| + | #Select PDE Tools->API Tools Setup. | ||
| + | #Follow the prompts, select the plugin projects that you want to add API Tooling too. | ||
| + | #If you haven't already create your Base Line entries. | ||
| + | |||
| + | Once completed, the API tooling builders will run, and report any errors in the Problems view. All projects that have errors will be marked with the standard error markers. | ||
| + | |||
| + | |||
| + | [[Category:XSL Tools]] [[Category:How to ...for WTP Developers| ]] | ||
Latest revision as of 15:18, 8 October 2008
For developing the XSL Tools plugins, all XSL Tools committers and contributors should have a Base Line eclipse installation installed. XSL Tools plugins have PDE's API Tooling enabled to help catch API breakages and versioning errors.
Setup API Tooling
For information on setting up API tooling see the following article:
https://www.ibm.com/developerworks/opensource/library/os-eclipse-api-tools/
Eclipse 3.4 JEE package should be the base line along with XSL Tools 0.5 added to that package.
Make sure to set up your Base Line reference in the Prefences->Plugin-Development->API Base Line
The name should be WTP 3.0.
Adding PDE API Tooling to a Plugin
- Select a project plugin, and right click.
- Select PDE Tools->API Tools Setup.
- Follow the prompts, select the plugin projects that you want to add API Tooling too.
- If you haven't already create your Base Line entries.
Once completed, the API tooling builders will run, and report any errors in the Problems view. All projects that have errors will be marked with the standard error markers.