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

Bug 479907

Summary:	Classes in Added External Class Folder are ignored
Product:	[Eclipse Project] JDT	Reporter:	Alekos Psimikakis <alsims>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	jarthana, sptaszkiewicz
Version:	4.4.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Alekos Psimikakis

2015-10-16 02:10:21 EDT

In configuring a build path, I have added an External Class Folder containing all the classes needed for the main class to be compiled and run (this is verified!)
Yet, I continue to see "XXX cannot be resolved to a type" errors. Not a single class from that folder is accepted/recognized ...
As an alternative, I have also added the necessary .jar files needed for the main class to be compiled. The result is the same.
Note than I can use javac.exe and java.exe with those .jar files from the command prompt in Windows 7 (i.e. outside Eclipse) and everything works fine.

What else is needed (that is not evident)?

Eclipse version: Luna Service Release 2 (4.4.2)
JDK version: jdk1.8.0_45
OS: Windows 7

Alekos

Comment 1 Jay Arthanareeswaran

2015-10-16 05:20:32 EDT

Does it happen with all the projects or just one project? Have you tried a clean + build? What else do you have in your build path? Which version of JRE? And lastly, have you installed any other plugins in your eclipse set-up?

Comment 2 Alekos Psimikakis

2015-10-16 06:11:14 EDT

To  Jay Arthanareeswaran:

Thank you for your comment.

I have tried with different projects that use external (extra) classes
I don't know about clean build ... I have tried a lot of times with a clean Eclipse, that is quitting and restarting.
I have nothing else in the build path except the added external class path.
JRE environment: I have already mentioned that. It's 1.8.
If I have installed any other plugins??? Yes, of course.

OK, again thanks, but this kind of debugging a problem rarely helps. It's like looking around blindfold. Only someone who has actually encountered this problem, or at least he/she knows why this problem happens, can solve it.

Alekos

Comment 3 Eclipse Genie

2020-03-29 11:34:16 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.