Bug 80224 - provide quickfix or other help for "The type ... cannot be resolved. It is indirectly referenced from required .class files" [quick fix]
Summary: provide quickfix or other help for "The type ... cannot be resolved. It is in...
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on: 80243
Blocks:
  Show dependency tree
 
Reported: 2004-12-05 16:16 EST by Ralf Hauser CLA
Modified: 2010-05-24 01:47 EDT (History)
0 users

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 Ralf Hauser CLA 2004-12-05 16:16:45 EST 
I copied a class from somewhere else, put into a package of mine and commented
out many methods and imports.

Now I am getting this error on line 0.

It appears that this comes from a dependency that is no more there. I tried
clean and rebuild, and it is still there

RFE:
- say which .class file references it
- add a quick-fix to remove the dependency
Comment 1 Ralf Hauser CLA 2004-12-05 16:28:19 EST 
the problem was inside a javadoc comment - once I removed the line

     * @see org.apache.mailet.Mailet# service(org.apache.mailet.Mail)

which was inside a comment, it no longer complained and did compile.
Comment 2 Ralf Hauser CLA 2004-12-06 00:44:26 EST 
it even turned out that injecting spaces into the path didn't fix it, however
breaking up the "see" did help.

     * @s ee org.apache.mailet.Mailet#service(org.apache.mailet.Mail)

fixes it while

     * @see org.apache. mailet.Mailet# service(org.apache. mailet.Mail)
doesn't
Comment 3 Dirk Baeumer CLA 2004-12-06 04:39:13 EST 
Filed a bug against JDT-Core for the request of mentioning the referenced class
file.

A quick fix is an enhancement.
Comment 4 Ralf Hauser CLA 2005-02-21 03:03:28 EST 
would be great to know which JDT Core Bug Dirk had filed. Possibly this is
already fixed?

The error messages here can also become very misleading if a corrupt jar-file is
taken as a library ==> see Bug 85940
Comment 5 Martin Aeschlimann CLA 2005-03-07 12:25:50 EST 
will reopen as soon as there is progress on bug 80243
Comment 6 Denis Roy CLA 2009-08-30 02:08:12 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.
Comment 7 Ralf Hauser CLA 2010-05-24 01:47:27 EDT 
see also bug 280469