Community
Participate
Working Groups
When importing plug-ins as binaries with attached source, or importing as source, we need to consider whether API tooling should be turned on for those plug-ins and how to set up the API descriptoins properly.
Binary import works (a .api_description is present and used). Importing as source does not work - the project is not created with an API tooling nature. I guess PDE UI should add the nature if it finds a .api_description file when importing. Moving to PDE UI, since the import operation is there. This is not critical. The user can turn on API tooling after the fact, if wanted (with PDE Tools > Set up API Tooling).
The import process should also remove the .api_description from the project root. This file is designed to be a static file. The dynamic api description is located in the .metadata folder.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
