Bug 7085 - Build errors when adding the JUnit example project
Summary: Build errors when adding the JUnit example project
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 major (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-19 06:37 EST by Erich Gamma CLA
Modified: 2002-03-05 06:28 EST (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 Erich Gamma CLA 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 CLA 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 CLA 2002-01-10 06:47:22 EST 
It is critical since this is part of the getting started experience.
Comment 3 Philipe Mulet CLA 2002-01-23 06:58:02 EST 
This is our well-known defect with unitialized classpath variables.
Comment 4 Philipe Mulet CLA 2002-03-05 06:28:06 EST 
Fixed by introducing classpath variable initializers (also see bug 3303).