Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333896

Summary:	errors in workspace on upgrading to i0104
Product:	[Eclipse Project] PDE	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Olivier_Thomann, remy.suen
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Jeff McAffer

2011-01-10 13:46:50 EST

I recently used i0104 to open a workspace previously developed using m4. Where there were no errors in the workspace with m4 there are errors with i0104.  Confusingly, the problems view does not show any errors but there are red Xs on various projects.  

This is not a case of stale state.  I did a clean build, open closed projects, ... and the errors persisted.  Switching back to m4 and doing a clean build removes the errors.  moving then to i0104 causes the errors to return.

Since there is no listing in the problems view there is no way to tell where the errors are originating.  My suspicion is either JDT or PDE (api tooling). I'm putting this in JDT Core since Olivier seems to hang out in both areas.

Comment 1 Olivier Thomann

2011-01-10 13:58:28 EST

Do you have a way to produce a reproducable test case ?

Comment 2 Jeff McAffer

2011-01-10 15:55:27 EST

A bit more poking around and some help from friends show that I did not have an API baseline set for the for the workspace.  Setting the baseline made all the errors go away. 

So now this is a problem whereby the error relating to not having a baseline set was not showing up anywhere that a user could see.  Interesting, another user in a similar situation did get entries in their Problems View. 

Moving this to PDE...

Comment 3 Eclipse Genie

2019-09-14 15:01:04 EDT

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.