Community
Participate
Working Groups
Created attachment 184333 [details] My API Baselines pref page I got slapped by Dani on bug 326926, comment 22 for not having the API Tools enabled. I do have couple of baselines defined, but they got out-dated once I moved them to a different location, which I didn't know since the tool gave me no info about it. Isn't that case the same as not defining an API baseline at all?
Created attachment 184334 [details] Out-dated API Baseline for 3.6 What's interesting about the dialog is that the location field has been cleared even though after I migrated to a new machine I'm using the exact same location for my Eclipses.
Marking as 'major' because - there's also no problem reported that there is no baseline defined in the workspace - nothing in .log - the preference page does not indicate a problem
I've had problems in the past that might be related (bug 307750), and I agree this is major. API Tooling seems to cache information somehow. Even during a "clean build", the cache doesn't seem to be cleared completely, which leads to missing errors in configuration / target platform / baseline that should be reported.
We should look into this during 3.7.
*** Bug 322890 has been marked as a duplicate of this bug. ***
Bumping to 3.8.
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.
