Bug 288224 - imports (to referenced projects) suddenly lost
Summary: imports (to referenced projects) suddenly lost
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.13 M3   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2009-09-01 04:11 EDT by Michael M CLA
Modified: 2019-08-20 23:17 EDT (History)
3 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 Michael M CLA 2009-09-01 04:11:24 EDT 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.11) Gecko/2009061212 Iceweasel/3.0.12 (Debian-3.0.12-1)
Build Identifier: M20090211-1700

Sometimes suddenly the project can't find some imports. Imports are just from the same project and/or from a referenced one.

Project setup is:
Java EJB Application
Java Client (referenes the ejb app)

Effected is only the Client, so i think it has something todo with the reference to the ejb application.

The only workaround that helped, was to delete the project and check it out from the repository again. After that, everything is working fine again.

I hav this problem also with the current galileo release and with a current galileo release on a mac.

The problem occurs at least once a day. Even without user interaction. (Go to the coffee-making facility, come back, have a lot of fun with hunderds of import errors).

Reproducible: Sometimes

Steps to Reproduce:
So that the problem occurs sometimes without user interaction, it's hard to give some reproduction steps.
Comment 1 Olivier Thomann CLA 2010-01-05 09:36:56 EST 
Please try to use the debug tracing for jdt.core.

Save the following file into a ".options" file that you put into the same folder as the Eclipse executable.

org.eclipse.jdt.core/debug=true
org.eclipse.jdt.core/debug/cpresolution=true
org.eclipse.jdt.core/debug/cpresolution/failure=true
Comment 2 Olivier Thomann CLA 2010-01-05 09:37:20 EST 
You need: -debug -consolelog on the Eclipse command line.
Comment 3 Eclipse Genie CLA 2019-07-24 10:27:58 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.
Comment 4 Stephan Herrmann CLA 2019-07-24 17:45:37 EDT 
Nothing we can do without further information.
Comment 5 Manoj N Palat CLA 2019-08-20 23:17:41 EDT 
Verified for Eclipse 2019-09 (4.13) M3 with Build id: I20190820-1800