Bug 64538 - CoreException from JavaBuilder loading platform-ui from HEAD
Summary: CoreException from JavaBuilder loading platform-ui from HEAD
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-28 08:40 EDT by Tod Creasey CLA
Modified: 2004-06-07 09:59 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tod Creasey CLA 2004-05-28 08:40:25 EDT
20040528

I got this exception to my log when I loaded platform-ui into a fresh 
workspace HEAD. I am not sure if there is a problem in HEAD or if this is a 
builder issue

!MESSAGE JavaBuilder handling CoreException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: 
Resource /org.eclipse.ui.workbench/bin/org/eclipse/ui/internal already exists.
	at org.eclipse.core.internal.resources.Resource.checkDoesNotExist
(Resource.java:297)
	at org.eclipse.core.internal.resources.Resource.checkDoesNotExist
(Resource.java:270)
	at org.eclipse.core.internal.resources.Folder.assertCreateRequirements
(Folder.java:25)
	at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
	at org.eclipse.core.internal.resources.Folder.create(Folder.java:119)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.createFolder
(AbstractImageBuilder.java:255)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.writeClassFile
(AbstractImageBuilder.java:441)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.acceptResult
(AbstractImageBuilder.java:115)
	at org.eclipse.jdt.internal.compiler.Compiler.compile
(Compiler.java:341)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:203)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:153)
	at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build
(BatchImageBuilder.java:49)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll
(JavaBuilder.java:213)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:136)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:558)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:615)
	at org.eclipse.core.runtime.Platform.run(Platform.java:758)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:154)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:246)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:199)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:226)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:615)
	at org.eclipse.core.runtime.Platform.run(Platform.java:758)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:229)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop
(BuildManager.java:265)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:294)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild
(AutoBuildJob.java:153)
	at org.eclipse.core.internal.events.AutoBuildJob.run
(AutoBuildJob.java:207)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Comment 1 Kent Johnson CLA 2004-05-31 11:32:57 EDT
The builder dumps CoreExceptions to the log so we can track them down... its 
not a bug in that we converted the exception into a problem marker, telling 
the user about the problem.

The question is what we were you doing at the time which caused the 
CoreException? Can you reproduce it? Did you have other applications open 
which were reading/writing to the output folder of the project?
Comment 2 Tod Creasey CLA 2004-05-31 11:40:14 EDT
I was just loading from CVS. I suspect it was due to the builder cancelling 
problems that got fixed in 20040529
Comment 3 Frederic Fusier CLA 2004-06-07 07:49:15 EDT
Tod, can you let us know if this issue still happens with RC1?
Please reopen if this is the case, thx.
Comment 4 Tod Creasey CLA 2004-06-07 08:16:15 EDT
I haven't seen it since the builder issues were fixed.
Comment 5 Frederic Fusier CLA 2004-06-07 09:57:28 EDT
OK. I'll reopen it to change the state, thx
Comment 6 Frederic Fusier CLA 2004-06-07 09:59:54 EDT
So finally consider this issue as not reproduceable