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

Bug 15972

Summary:	JAR file from classpath not indexed
Product:	[Eclipse Project] JDT	Reporter:	Peter Burka <peter_burka>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	Olivier_Thomann
Version:	2.0
Target Milestone:	2.0 F3
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Peter Burka

2002-05-14 16:39:49 EDT

Build M5.

I loaded a project from CVS.

The project has a number of references to external jar files like 
ECLIPSE_HOME/plugins/com.ibm.etools.ctc.flow.common/runtime/flowcommon.jar. 
(Note that ECLIPSE_HOME refers to an second Eclipse install).

Most of these work just fine, but flowcommon.jar is problematic. Although the 
compiler can find classes in this jar and compile code against it, Code 
Assist, and 'Show problems before compiling' cannot find classes in it. 
References are flagged as 'unresolved' by the early problem finder, Code 
Assist won't make any suggestions for them, and I can't even find the classes 
from the 'Open Type' dialog.

I noticed that the jar file is included in the classpath, but it does not show 
up as a jar in the Packages view. I tried removing it from the classpath and 
re-adding it, and this cuased it to start appearing in the Packages view, but 
did not fix the other problems.

I then exited Eclipse, deleted all of the index files 
in .metadata/.plugins/org.eclipse.jdt.core and restarted. This did not seem to 
help. I then 'Rebuilt All'; this seems to have fixed the problems.

Comment 1 Olivier Thomann

2002-05-14 17:28:37 EDT

I could not reproduce the problem using this jar file as an external jar of a 
Java project. I can successfully retrieve the FlowCommonUtils class. Code 
assist could retrieve this class. That wasn't the case in the Peter's 
workspace. I suspect either a problem during the initial build or the indexes 
files got corrupted somehow.

Comment 2 Philipe Mulet

2002-05-14 18:22:25 EDT

Did an exit then restart fix the problem ? Or even manually deleting the index 
files change the behavior ?

Comment 3 Peter Burka

2002-05-15 10:44:10 EDT

I was able to fix the problem by:

-exiting
-deleting all index files
-restarting
-rebuilding all projects

Comment 4 Philipe Mulet

2002-05-15 12:27:58 EDT

Did you happen to close/reopen some projects ? (and likely exit with closed 
projects)

Comment 5 Peter Burka

2002-05-15 13:33:06 EDT

I do have closed projects, and they were closed when I exited. I don't recall 
opening them lately, although I think that I did close one that had been open 
yesterday.

Comment 6 Philipe Mulet

2002-05-16 06:33:27 EDT

Was it per chance referring to the offending JAR ?

Comment 7 Peter Burka

2002-05-16 11:06:56 EDT

No. The closed project had no references to the offending JAR.

Comment 8 Philipe Mulet

2002-06-06 11:03:12 EDT

Peter - can you reproduce this defect with last build (0606) ? We haven't been 
able to reproduce this defect, but solved a couple issues in this area which 
could have lead to missing indexing a JAR referenced through a variable (due to 
concurrency issue). see bug 19303.

Comment 9 Peter Burka

2002-06-06 11:26:56 EDT

I haven't seen this problem in F2 yet

Comment 10 Philipe Mulet

2002-06-10 10:16:15 EDT

Ok, closing as duplicate of 19303. Please reopen if the symptoms were 
reappearing.

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