Bug 23076 - compilation does not create class files!!!
Summary: compilation does not create class files!!!
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows All
: P3 blocker (vote)
Target Milestone: 2.1   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-02 05:35 EDT by MH CLA
Modified: 2013-10-23 06:19 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MH CLA 2002-09-02 05:35:14 EDT
every once in a while, compilation does NOT create class files! even "build 
all" just pops up the progress dialog for a second and disappears. NO ERROR! 
but the build directory only contains the packages (directories) and no class 
files! i have to close eclipse and delete all files under my output directory 
(classes directory) and try again ... after several times, eclipse gets back to 
create class files. THIS IS CRITICAL!!!
Comment 1 Philipe Mulet CLA 2002-09-02 07:29:22 EDT
Have never observed this behavior. Do you have steps to reproduce, so that we 
can investigate ?

Comment 2 Kent Johnson CLA 2002-09-04 14:06:32 EDT
Are there any build errors on the project themselves? Or walkbacks in your .log 
file?

Is your workspace on a network drive which is temporarily running out of disk 
space?
Comment 3 MH CLA 2002-09-05 12:39:29 EDT
no network drive, nothing special. just one Windows NT 4.0 workstation running eclipse 2.0. a 
coworker has noticed the same effect on his (different) computer with eclipse 2.0... :-(
Comment 4 Kent Johnson CLA 2002-09-06 14:29:31 EDT
Well we're going to need some help so we have somewhere to start... we haven't 
heard of anything like this.

Please check your .log file whenever this happens and attach any walkbacks you 
find. Include your project's .classpath files so we can see how your projects 
are configured.

Also describe the machines that have this problem: OS version, VM version, etc.
Comment 5 MH CLA 2002-09-13 09:49:00 EDT
It happened again! Here's the latest entry of the eclipse log:


!SESSION Sep 12, 2002 14:45:54.198 ---------------------------------------------
java.version=1.3.1_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86 -install 
file:C:/Programme/eclipse/
!ENTRY org.eclipse.ui 4 0 Sep 12, 2002 14:45:54.198
!MESSAGE Exception creating image descriptor for: 
org.eclipse.search.searchmarker
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Marker id: 5472 not 
found.
	at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:53)
	at org.eclipse.core.internal.resources.Marker.getType(Marker.java:168)
	at org.eclipse.core.internal.resources.Marker.isSubtypeOf
(Marker.java:186)
	at 
org.eclipse.ui.internal.registry.MarkerImageProviderRegistry.getImageDescriptor
(MarkerImageProviderRegistry.java:90)
	at org.eclipse.ui.internal.model.WorkbenchMarker.getImageDescriptor
(WorkbenchMarker.java:30)
	at org.eclipse.ui.texteditor.MarkerAnnotation.getImage
(MarkerAnnotation.java:251)
	at org.eclipse.jdt.internal.ui.javaeditor.JavaMarkerAnnotation.getImage
(JavaMarkerAnnotation.java:181)
	at org.eclipse.ui.texteditor.MarkerAnnotation.paint
(MarkerAnnotation.java:196)
	at org.eclipse.jface.text.source.AnnotationRulerColumn.doPaint
(AnnotationRulerColumn.java:325)
	at org.eclipse.jface.text.source.AnnotationRulerColumn.doubleBufferPaint
(AnnotationRulerColumn.java:217)
	at org.eclipse.jface.text.source.AnnotationRulerColumn.redraw
(AnnotationRulerColumn.java:355)
	at org.eclipse.jface.text.source.AnnotationRulerColumn$4.run
(AnnotationRulerColumn.java:342)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:31)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:95)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1506)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1294)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.runEventLoop
(EventLoopProgressMonitor.java:89)
	at 
org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.internalWorked
(EventLoopProgressMonitor.java:62)
	at org.eclipse.core.runtime.ProgressMonitorWrapper.internalWorked
(ProgressMonitorWrapper.java:76)
	at org.eclipse.core.runtime.SubProgressMonitor.internalWorked
(SubProgressMonitor.java:143)
	at org.eclipse.core.runtime.ProgressMonitorWrapper.internalWorked
(ProgressMonitorWrapper.java:76)
	at org.eclipse.core.runtime.SubProgressMonitor.internalWorked
(SubProgressMonitor.java:143)
	at org.eclipse.core.runtime.ProgressMonitorWrapper.internalWorked
(ProgressMonitorWrapper.java:76)
	at org.eclipse.core.runtime.SubProgressMonitor.internalWorked
(SubProgressMonitor.java:143)
	at org.eclipse.core.runtime.SubProgressMonitor.worked
(SubProgressMonitor.java:167)
	at org.eclipse.jdt.internal.core.builder.BuildNotifier.updateProgress
(BuildNotifier.java:230)
	at 
org.eclipse.jdt.internal.core.builder.BuildNotifier.updateProgressDelta
(BuildNotifier.java:239)
	at org.eclipse.jdt.internal.core.builder.BuildNotifier.compiled
(BuildNotifier.java:107)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.acceptResult
(AbstractImageBuilder.java:131)
	at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:349)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:219)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:166)
	at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.build
(IncrementalImageBuilder.java:108)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildDeltas
(JavaBuilder.java:181)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:109)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:831)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:831)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java:733)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1366)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:78)
	at org.eclipse.ui.texteditor.AbstractTextEditor.performSaveOperation
(AbstractTextEditor.java:2327)
	at 
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.performSaveOperatio
n(CompilationUnitEditor.java:664)
	at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.doSave
(CompilationUnitEditor.java:712)
	at org.eclipse.ui.internal.EditorManager$11.run(EditorManager.java:987)
	at org.eclipse.ui.internal.EditorManager$8.run(EditorManager.java:856)
	at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:299)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
	at org.eclipse.jface.window.ApplicationWindow$1.run
(ApplicationWindow.java:394)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
	at org.eclipse.jface.window.ApplicationWindow.run
(ApplicationWindow.java:391)
	at org.eclipse.ui.internal.WorkbenchWindow.run
(WorkbenchWindow.java:1105)
	at org.eclipse.ui.internal.EditorManager.runProgressMonitorOperation
(EditorManager.java:862)
	at org.eclipse.ui.internal.EditorManager.saveEditor
(EditorManager.java:992)
	at org.eclipse.ui.internal.WorkbenchPage.saveEditor
(WorkbenchPage.java:1922)
	at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:32)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:407)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent
(ActionContributionItem.java:361)
	at org.eclipse.jface.action.ActionContributionItem.access$0
(ActionContributionItem.java:352)
	at 
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent
(ActionContributionItem.java:47)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1177)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1160)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:775)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:248)
	at org.eclipse.core.launcher.Main.run(Main.java:698)
	at org.eclipse.core.launcher.Main.main(Main.java:534)
!ENTRY org.eclipse.core.resources 4 376 Sep 12, 2002 14:45:54.198
!MESSAGE Marker id: 5472 not found.
Comment 6 MH CLA 2002-09-18 07:57:44 EDT
Once again, no classes were created. This time, i found the following error in 
the .log file:


*******
!SESSION Sep 18, 2002 14:11:52.500 ---------------------------------------------
java.version=1.3.1_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86 -install 
file:D:/Programme/eclipse/
!ENTRY org.eclipse.jdt.core 4 4 Sep 18, 2002 14:11:52.510
!MESSAGE JavaBuilder handling ImageBuilderInternalException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build
(BatchImageBuilder.java:33)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll
(JavaBuilder.java:170)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:94)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:831)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:831)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.build
(Workspace.java:142)
	at org.eclipse.ui.actions.GlobalBuildAction$1.run
(GlobalBuildAction.java:156)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
!ENTRY org.eclipse.core.resources 4 4 Sep 18, 2002 14:11:52.510
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Sep 18, 2002 14:11:52.510
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
**************
Comment 7 Philipe Mulet CLA 2002-09-18 08:46:52 EDT
Do you have other tools running and holding pointers to files located inside 
your output folder ?

Note that a task should have been added to report this issue - shouldn't it 
Kent ?
Comment 8 MH CLA 2002-09-19 02:51:00 EDT
nope, no other tasks. i have CVS (WinCVS) also running in the background, but 
my classes directory is not in the CVS, so eclipse is the only task handling my 
classes directory (that is the build output directory of my project).
Comment 9 Kent Johnson CLA 2002-09-19 10:15:25 EDT
I realize you may not remember, but what time did the problem show up vs. the 
time of the stack trace in the .log file?

There are some stack traces written to the .log file which were handled inside 
Eclipse and not considered bugs or failures.
Comment 10 Kent Johnson CLA 2002-11-18 16:43:46 EST
Is this still happening?

Do you have any other walkbacks?
Comment 11 MH CLA 2002-11-19 05:42:28 EST
it still happens once in a while. here the last occurence in the .log file:


!SESSION Okt 08, 2002 14:43:27.560 ---------------------------------------------
java.version=1.3.1_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86 -install 
file:D:/Programme/eclipse/
!ENTRY org.eclipse.jdt.core 4 4 Okt 08, 2002 14:43:27.560
!MESSAGE JavaBuilder handling CoreException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.isWorthBuilding
(JavaBuilder.java:464)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:92)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.build
(Workspace.java:142)
	at org.eclipse.ui.actions.GlobalBuildAction$1.run
(GlobalBuildAction.java:156)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
!ENTRY org.eclipse.core.resources 4 4 Okt 08, 2002 14:43:27.560
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Okt 08, 2002 14:43:27.560
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
!ENTRY org.eclipse.jdt.core 4 4 Okt 08, 2002 14:43:31.816
!MESSAGE JavaBuilder handling CoreException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.isWorthBuilding
(JavaBuilder.java:464)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:92)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:232)
	at org.eclipse.core.internal.resources.Project.build(Project.java:85)
	at org.eclipse.ui.actions.BuildAction.invokeOperation
(BuildAction.java:151)
	at org.eclipse.ui.actions.WorkspaceAction.execute
(WorkspaceAction.java:112)
	at org.eclipse.ui.actions.WorkspaceAction$1.execute
(WorkspaceAction.java:269)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run
(WorkspaceModifyOperation.java:64)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1378)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:78)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
!ENTRY org.eclipse.core.resources 4 4 Okt 08, 2002 14:43:31.816
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Okt 08, 2002 14:43:31.816
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
!ENTRY org.eclipse.jdt.core 4 4 Okt 08, 2002 14:44:32.524
!MESSAGE JavaBuilder handling CoreException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.isWorthBuilding
(JavaBuilder.java:464)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:92)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java:745)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1383)
	at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run
(WorkbenchRunnableAdapter.java:32)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
!ENTRY org.eclipse.core.resources 4 4 Okt 08, 2002 14:44:32.524
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Okt 08, 2002 14:44:32.524
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
!ENTRY org.eclipse.jdt.core 4 4 Okt 08, 2002 14:46:06.739
!MESSAGE JavaBuilder handling ImageBuilderInternalException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build
(BatchImageBuilder.java:33)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll
(JavaBuilder.java:170)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:99)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java:745)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1383)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:78)
	at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:299)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
	at org.eclipse.jface.dialogs.ProgressMonitorDialog.run
(ProgressMonitorDialog.java:376)
	at 
org.eclipse.jdt.internal.ui.preferences.BuildPathsPropertyPage.performOk
(BuildPathsPropertyPage.java:140)
	at org.eclipse.jface.preference.PreferenceDialog.okPressed
(PreferenceDialog.java:577)
	at org.eclipse.jface.preference.PreferenceDialog.buttonPressed
(PreferenceDialog.java:175)
	at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:398)
	at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:87)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:562)
	at org.eclipse.jface.window.Window.open(Window.java:542)
	at org.eclipse.ui.dialogs.PropertyDialogAction.run
(PropertyDialogAction.java:159)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:407)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent
(ActionContributionItem.java:361)
	at org.eclipse.jface.action.ActionContributionItem.access$0
(ActionContributionItem.java:352)
	at 
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent
(ActionContributionItem.java:47)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1256)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1239)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:775)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:248)
	at org.eclipse.core.launcher.Main.run(Main.java:698)
	at org.eclipse.core.launcher.Main.main(Main.java:534)
!ENTRY org.eclipse.core.resources 4 4 Okt 08, 2002 14:46:06.749
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Okt 08, 2002 14:46:06.749
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
!ENTRY org.eclipse.jdt.core 4 4 Okt 08, 2002 14:46:10.124
!MESSAGE JavaBuilder handling ImageBuilderInternalException
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Problems encountered 
while deleting resources.
	at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:460)
	at 
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.scrubOutputFolder
(BatchImageBuilder.java:86)
	at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build
(BatchImageBuilder.java:33)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll
(JavaBuilder.java:170)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:99)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:392)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:839)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:211)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java:745)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1383)
	at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run
(WorkbenchRunnableAdapter.java:32)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)
!ENTRY org.eclipse.core.resources 4 4 Okt 08, 2002 14:46:10.124
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 1 org.eclipse.core.resources 4 273 Okt 08, 2002 14:46:10.124
!MESSAGE Could not delete: D:\data\deka\bav\prg\java\bin\classes\de.
Comment 12 Kent Johnson CLA 2002-11-19 11:33:33 EST
None of these walkbacks are bugs... they are all cases when we detected (& 
reported against the project) a build problem because there is another 
application holding onto resources in the output folder, which we're trying to 
delete.

Please double check the errors reported against the project whenever the build 
fails... you should find an error indicating that .class files or other 
resources could not be deleted.
Comment 13 Kent Johnson CLA 2002-11-20 15:26:01 EST
Closing until we can tell that this is not just a problem with another process 
holding onto files in the output folder, when we're trying to delete them.
Comment 14 MH CLA 2002-11-26 03:15:36 EST
so, even if some other process holds references to the class files, i consider 
this a bug as Eclipse just behaves as nothing went wrong, when building the 
project. a exception in the .log file is not enough as a developer does not 
show in the log on every compile cycle ;-)

as this is a build error (the classes were not created - no matter what 
reason), the gui should at least display a corresponding error to inform the 
developer that build was not successful.
Comment 15 Kent Johnson CLA 2002-11-26 10:50:11 EST
"so, even if some other process holds references to the class files, i consider 
this a bug as Eclipse just behaves as nothing went wrong"

That's incorrect.

Everytime these messages are logged, we also create an error that appears in 
the task list. We tag the project with an error that says:

"The project was not built. It may be inconsistent, if so ensure no other tool 
is browsing the output directory, then try refreshing this project and 
rebuilding it"
Comment 16 MH CLA 2002-11-27 03:10:58 EST
task list? i've seen that but have no use of it as it is cluttered with CVS 
messages. but besides this: if this is printed in this task list, why doesn't 
the task list pop up? if this occurs, how do i know if there are some entries 
in a task view? the task view does not pop up on this, so i have to think, that 
build was successful! i call this a very basic feature, as not all developers 
know about this task list or even if they know about it, they don't use it or 
look into it after each compile cycle.

at least, if there is such an error, this task list should pop up. there should 
be at least an automatic viewing of the error without the developer forced to 
look somewhere himself if the build was successful. isn't that understandable?
Comment 17 Kent Johnson CLA 2002-11-27 10:34:40 EST
"i've seen that but have no use of it as it is cluttered with CVS messages."

A red error X is attached to the project itself in the packages view to tell 
you that the build failed... or did you close that too? ;)

You can also set the filters in the task list to remove CVS problems. The task 
list is important and should not be closed.
Comment 18 MH CLA 2002-11-28 03:32:09 EST
okay, i see that i can't convince you for a popup dialog like "build failed - 
see task view" (which automatically pops up/comes to front. then i have to 
convince my collegues that they have to carefully watch the project tree node 
and the task view, as this occured on other computers too and the developers 
were surprised that their war/ear files (build from ant tasks) were empty 
because of missing classes. so the current behaviour is not that clear/obvious.
Comment 19 Kent Johnson CLA 2002-11-28 10:00:47 EST
"they have to carefully watch the project tree node"

Please describe your workspace/perspectives:

1. Which perspective do you work in by default? Is it the Java perspective?

2. Do you never watch the builder progress dialog? If you do then do you not 
see it increasing the error count & aborting prematurely?

3. How often or how many errors (ie. red X's) do you have in your project? In 
other words, do you often work with dozens of errors left to be fixed?

If not, then it should be obvious when 'new' errors are detected. The further 
up the project, the worse the error.
Comment 20 MH CLA 2002-11-29 03:38:43 EST
> 1. Which perspective do you work in by default? Is it the Java perspective?

Java Perspective

> 2. Do you never watch the builder progress dialog? If you do then do you not 
> see it increasing the error count & aborting prematurely?

You mean the little dialog that pops up when doing a Project > Rebuild Project? 
We barely use this, as saving the current editor automatically checks for 
syntax. when we build the broject, we have our own ant tasks. 

>3. How often or how many errors (ie. red X's) do you have in your project? In 
>other words, do you often work with dozens of errors left to be fixed?

that depends on the developer. i try to fix the red crosses as soon as they 
appear (another developer does not). and i noticed sometimes that the root node 
(project name) had a red cross. but i wasn't able to figure out what it was or 
how to fix it, as the red cross did not appear lower in the tree, there is no 
tooltip, and double click also didn't do anything. so i left this root-node-red 
cross and waited till it disappeared by itself.

perhaps this was the indication i was looking for and it doesn't tell me what's 
wrong. (again: tooltip or popup of task view with error would be nice ;-)
Comment 21 Kent Johnson CLA 2002-11-29 10:16:33 EST
"We barely use this, as saving the current editor automatically checks for 
syntax. when we build the broject, we have our own ant tasks."

Sorry, what did you mean by this? Do you have the option Window->Preferences-
>Workbench->Perform build automatically... enabled or disabled?

If its enabled then whenever you save changes in the editor, a build is 
performed. You do not need ant tasks to build your code. If you do want to 
rebuild your world, then use Project->Rebuild All.

"perhaps this was the indication i was looking for"

The next time you see a red X on a project, check the tasks view. If you set 
its filter to "Any resource in same project", you will see the error, since we 
delete all other errors so this major error is the only one left.
Comment 22 MH CLA 2002-11-29 11:12:00 EST
"Sorry, what did you mean by this? Do you have the option Window->Preferences-
>Workbench->Perform build automatically... enabled or disabled?"

Enabled.

"If its enabled then whenever you save changes in the editor, a build is 
performed. You do not need ant tasks to build your code. If you do want to 
rebuild your world, then use Project->Rebuild All."

i know. that's why we don't use "rebuild all", we just save the changes. what i 
meant with the ant tasks is, that we have ant tasks that build JARs/WARs and 
these tasks depend on other tasks, also compile-tasks. so, whenever i want to 
test my servlet, i just run my ant task "J2EE.deploy" which compiles the 
project, builds the jar, war and ear files, deploys to J2EE... info: our ant 
build.xml is not Eclipse specific, the targets need to run also without 
Eclipse, so we also have the compile targets. so, we also have a 
target "create.WAR" and for speed reasons, this and some other targets don't do 
all the compile stuff again and again. the classes are expected to be created. 
in the error case this bugzilla report is about, sometimes Eclipse does not 
create the class files but deletes them - which is another strange behaviour of 
Eclipse: it can't create the class files because some other process is holding 
reference to them (so _your_ opinion) but on the other hand it is able to 
delete the classes - now THIS is strange, isn't it? remember the original 
error: Eclipse does not create class files ... the output directory of the 
project is empty!
Comment 23 Kent Johnson CLA 2002-11-29 11:28:26 EST
I remember... as far as: "it is able to delete the classes - now THIS is 
strange, isn't it?"

Which would you prefer:

1. Leave an inconsistent set of .class files in the output folder so it takes 
hours to debug the numerous problems that are caused by the mis-matched files, 
or

2. No .class files at all so you don't waste your time debugging bogus code?

Have you ever tried debugging .class files that don't match the source files 
anymore?

Its not a lot of fun...
Comment 24 Mark Jeronimus CLA 2013-10-23 06:16:49 EDT
I have the same iossue.

Lo log file is created.

Deleting all class files, even the entire bin folder doesn't fix it.

Clean doesn't fix it, it just skips compiling the affexted project.

I found a workaround. Delete the project, then re-import it. Don't change anything.
Comment 25 Mark Jeronimus CLA 2013-10-23 06:19:26 EDT
I have the same issue.

No log file is created.

Deleting all class files, even the entire bin folder doesn't fix it.

Clean doesn't fix it, it just skips compiling the affected project.

I found a workaround. Delete the project, then re-import it. Don't change anything.