Bug 7085

Summary:	Build errors when adding the JUnit example project
Product:	[Eclipse Project] JDT	Reporter:	Erich Gamma <erich_gamma>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P1
Version:	2.0
Target Milestone:	2.0 M4
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Erich Gamma

2001-12-19 06:37:21 EST

The build starts before the Java UI plugin is activated and the class path 
initialized. Workaround is to rebuild again.

Comment 1 Martin Aeschlimann

2002-01-10 06:18:58 EST

This is what happens:
(code in org.eclipse.jdt.ui.examples.projects)
- A project is created with natures specified in the plugin.xml (->includes jdt 
nature)
- Project content, including the .classpath file is imported (all in a 
workspacerunnable)
- This overwrite the existing classpath file. As the bug describes, the build 
triggered by the import a rebuild does not use the new .classpath file.
- Rebuild: Errors are gone

moving to jdt.core

The change of .classpath should retrigger the build.

Comment 2 Erich Gamma

2002-01-10 06:47:22 EST

It is critical since this is part of the getting started experience.

Comment 3 Philipe Mulet

2002-01-23 06:58:02 EST

This is our well-known defect with unitialized classpath variables.

Comment 4 Philipe Mulet

2002-03-05 06:28:06 EST

Fixed by introducing classpath variable initializers (also see bug 3303).