Bug 6232

Summary:	Build problems: Internal error: null when compiling JDK source code
Product:	[Eclipse Project] JDT	Reporter:	Magnus Ihse Bursie <magnus.ihse.bursie>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.0 M2
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Magnus Ihse Bursie

2001-11-22 11:41:02 EST

I downloaded the JDK1.3.1 source code from Sun. I unpacked the tar.gz archive. 
Then I imported the java source code from the src\share\classes
directory into a newly created project "Sun JDK 1.3.1".

After turning off auto build and trying again, I could actually import the 
source files. :-) (Big improvement over old VA Java... feels good, thank you!)

However, I could never get the project to compile. I didn't really expect
that, since this is a really naïve approach, but it seems as Eclipse fails
before it really starts compiling. I get a lot of checking for compile
status and stuff, and then I got a message dialog with title "Build problems", 
saying "Internal error: null". 

I realize that the code probably is incomplete and perhaps not possible to 
compile, however, then Eclipse should respond with compilation errors, and not 
in this way.

Comment 1 Philipe Mulet

2001-11-23 18:40:15 EST

Did you get any stack trace in the .log file ? (inside the .metadata folder at 
the root of your workspace).

Comment 2 Philipe Mulet

2001-11-23 19:02:40 EST

I tried it and wasn't able to reproduce.

The workspace contains exactly one project with one source folder containing 
the expanded content of this JAR, and I obtain 1418 errors after build.

What is the exact classpath of your project ? Did you have another library on 
your path ? Which Eclipse build are you running ?

Comment 3 Philipe Mulet

2001-11-26 11:23:37 EST

Ok to close ?

Comment 4 Philipe Mulet

2002-01-09 12:50:48 EST

Closing. Please reopen if still active.