Bug 16436 - CoreException importing org.eclipse.ui.win32
Summary: CoreException importing org.eclipse.ui.win32
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC other
: P1 critical (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 17254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-20 10:46 EDT by Darin Swanson CLA
Modified: 2002-05-27 08:30 EDT (History)
1 user (show)

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 Darin Swanson CLA 2002-05-20 10:46:53 EDT 
20020519

Updating a workspace created on 20020515, I get the following core exception 
importing binary projects.  I was using the PDE tool and had selected add 
existing binary projects.

!STACK 1
Java Model Exception: Core Exception [code 271] File not found: c:\0515
\org.eclipse.ui.win32\.classpath.
	at org.eclipse.jdt.internal.core.JavaProject.loadClasspath
(JavaProject.java:1540)
	at org.eclipse.jdt.internal.core.JavaProject.getOutputLocation
(JavaProject.java:990)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.initializeBuilder
(JavaBuilder.java:356)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:89)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:383)
	at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code))
	at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code))
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:119)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:173)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:183)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:143)
	at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code))
	at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code))
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:157)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:208)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java(Compiled Code))
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1366)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportWizard$2.run
(PluginImportWizard.java:122)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
Comment 1 Nick Edgar CLA 2002-05-20 12:09:21 EDT 
Moving to JDT Core.
Comment 2 Philipe Mulet CLA 2002-05-20 14:06:08 EDT 
Duplicate of bug 16389. Moving to PDE since .classpath was deleted by it.
Comment 3 Nick Edgar CLA 2002-05-20 14:14:06 EDT 
Shouldn't the builder be resilient to a missing .classpath?
Comment 4 Philipe Mulet CLA 2002-05-20 17:35:43 EDT 
A missing .classpath file means no classpath, thus no point building.
Comment 5 Philipe Mulet CLA 2002-05-20 17:49:59 EDT 
We should abort the build more silently, but still abort if unable to get the 
classpath or the output location.
Comment 6 Kent Johnson CLA 2002-05-21 11:58:08 EDT 
This walkback was logged so we could track what CoreExceptions are being caught 
by the builder... its not a build failure.
Comment 7 Philipe Mulet CLA 2002-05-27 08:30:07 EDT 
*** Bug 17254 has been marked as a duplicate of this bug. ***