Community
Participate
Working Groups
When the API builder detects that there has been a change to the .api_filters file - i.e. a filter has been added or removed since the last build - we revert to doing a full build. This is a terrible waste, since we could just be rescanning the type the filter was added for (and any dependents as needed). All of the information we need to scan only the type the filter changed for is in the .api_filters file, we just have to make use of it.
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.