Bug 38054 - "Scrubbing Output Folder" occurs on a normal file save
Summary: "Scrubbing Output Folder" occurs on a normal file save
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: 3.0 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2003-05-23 11:59 EDT by Antony Brown CLA
Modified: 2009-08-30 02:06 EDT (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 Antony Brown CLA 2003-05-23 11:59:05 EDT 
Some of our developers are experiencing very long waits when they save a java 
source file. Instead of compiling that file, eclipse seems to scrub the output 
folder and then compile all classes that are required to compile the saved file.
This isn't happenning to all users, but once it does start happenning, we 
haven't found a way of stopping it (although some people have de-selected 
the "Perform Build automatically on resource modification"). 
I appreciate that this may be difficult to look at due to it's random nature, 
but hopefully this won't be the first report. I have looked for other similar 
reports but failed, apart from #10628, which briefly mentions a similar 
situation :
"Also my colleagues complain that the compilation is slow and that "scrubbing 
output folder" sometimes happens on normal file save (that should only trigger 
compilation)."
Comment 1 Philipe Mulet CLA 2003-05-23 12:24:25 EDT 
The output folder is updated during compilation. When a full build occurs (for 
some reason it wasn't able to perform incrementally), then it will clean the 
output folder. In 2.1, you can turn off the output folder cleaning (See 
preferences>Java>compiler>build path>scrub output folders on full build

In order to understand why full builds occur when only incremental builds 
should, please provide steps to reproduce. Alternatively, you can enable the 
Java builder trace and see what occurs.

In order to enable the tracing, launch Eclipse in debug mode using -debug and 
java.exe (to open console), with following options specified in .options file 
next to eclipse.exe:
org.eclipse.jdt.core/debug=true
org.eclipse.jdt.core/debug/builder=true
Comment 2 Philipe Mulet CLA 2003-06-02 06:27:39 EDT 
Side-question: which build are you using ? We changed the message 
from "scrubbing..." to "cleaning..." quite a while ago. I would suggest you use 
a recent build.
Comment 3 Philipe Mulet CLA 2003-06-11 11:40:03 EDT 
Please reopen once more information is available
Comment 4 Philipe Mulet CLA 2003-09-19 05:45:18 EDT 
Closing since no activity in past 3 months.
Comment 5 Denis Roy CLA 2009-08-30 02:06:41 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.