Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322890 - API Tooling preference page does not indicate if baseline code is missing
Summary: API Tooling preference page does not indicate if baseline code is missing
Status: CLOSED DUPLICATE of bug 331644
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-17 07:34 EDT by Beth Tibbitts CLA
Modified: 2010-12-06 11:36 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Beth Tibbitts CLA 2010-08-17 07:34:38 EDT 
I set up API tools against our baseline.
Some time after that, the code that my baseline pointed to got "unhooked" from the API Tools preference page baseline.  I didn't do anything to cause this that I know of.

Problems weren't showing up. I looked on the API baselines preference page and saw that the baseline was still there, so didn't know what was wrong.  Only when I hit the 'Edit' button and realized it was no longer pointing to my code snapshot did i realize what happened.

API Tools preference page needs an indicator that a baseline is not pointing to anything.
Comment 1 Darin Wright CLA 2010-08-18 10:31:19 EDT 
Do you mean the baseline referred to a location that got deleted/moved? Or do you mean that your baseline remained in the same location, but API tools was no longer able to "see" it?
Comment 2 Beth Tibbitts CLA 2010-08-19 15:52:57 EDT 
The latter.  The baseline remained in the same location, but API tools seemed to forget it was there.  The main UI page doesn't indicate that there is nothing behind the entry.
Comment 3 Darin Wright CLA 2010-08-20 09:34:36 EDT 
This may be a duplicate of bug 315092.
Comment 4 Dani Megert CLA 2010-12-06 11:36:15 EST 

*** This bug has been marked as a duplicate of bug 331644 ***