Re: [jdt-dev] OT: object info doesn't appear during holdover.

[linuxguy <linuxguy123@xxxxxxxxx>]

On Tue, 2006-12-19 at 20:24 +0100, Aaron Digulla wrote:
> linuxguy wrote:

> > I've been fighting with this problem for over a week and I've posted to
> > eclipse.tools.jdt and I still haven't gotten it resolved.
> 
> Please open a bug report on http://bugs.eclipse.org/bugs/ for things
> like this.

The thing is that you never know if its really a bug or not, so I
refrain from posting it as such. Can we explore a few things here
first ?

> > What do I do to make holder info and object completion work again ?
> 
> These things are called "tool tips" (the little yellow windows). In your
> bug report, you should include some additional info:
> 
> - What happens when you press F2 (which forces Eclipse to open a real
> window with the tool tip text).

Holding over a Display object and pressing F2 gives this:

org.eclipse.swt.widgets.Display
Note: This element neither has attached source nor attached Javadoc and
hence no information could be found.

> - Can you see something in the Javadoc view?

Javadoc view is empty.  Just yellow. 

> - Is there anything in the error log (see Window -> Views).

This ! Digest could not be parsed:Unable to retrieve remote reference
"http://download.eclipse.org/updates/3.2/digest.zip";. [Server returned
HTTP response code: "404 Not Found" for URL:
http://download.eclipse.org/updates/3.2/digest.zip.]

(I did a fresh install this AM.)

> - Maybe your problem is related to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=148872

OK, that bug says

"When a jar on the classpath becomes missing (or is typed in wrong), the
source path computation
fails. The source path page should show the error, and not abort computing the
entire source path if one jar is missing."

What does it mean by "when a jar on the classpath becomes missing" ?  What jar(s) is it speaking about ?
I opened up a brand new project and left everything as default.

FWIW, I can javac hello.jar and then java hello and it works. 

"Currently, and exception is logged, but nothing blows up. This problem also
exists in 3.1, so it's not a regression."

Where does this exception get logged ?  Will it list the offending jar(s) ?

One thing that bugs me is that I've wiped my computer clean of eclipse
as far as I know and reinstalled and this problem still exists, even in
a brand new project.  When I say wiped it clean, I mean I've deleted
the .eclipse file in my home dir and the workspace directory.  Is there
any other eclipse files hanging around somewhere ?  

Thanks.