Community
Participate
Working Groups
In an effort to improve the overall performance of API tools and expand its functionality we need to re-architect the way we handle API descriptions and profiles, as well as homogenize our descriptor framework. From the 3.5 plan: * Migrate architecture to support binary or source analysis - Currently, API tools only analyzes binaries. As we move to support source analysis we will leverage the bounded Java model element cache. We will use a similar caching strategy for analysis in a non-OSGi/non-workspace environment (i.e. releng-build).
This is related to my enhancement request https://bugs.eclipse.org/bugs/show_bug.cgi?id=312426
This enhancement request is about the actual information being analyzed - i.e. the ability to analyze .java files vs. class files (it's not about source vs. binary compatibility issues).
Ah, now I fully understand. In that case there is no direct relation, sorry. Except that implementing source analysis might make it possible to fully implement source compatibility analysis, and that might be a good time to differentiate between compatibility problem types.
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.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
