Bug 30609

Summary: Output folder scrubbing
Product: [Eclipse Project] JDT Reporter: George L. Smith <gsmith>
Component: CoreAssignee: Kent Johnson <kent_johnson>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: 2.1 RC1   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description George L. Smith CLA 2003-01-30 10:12:15 EST
When scrubbing the output folder, you should only scrub java class files. In a 
web application, it is common to put properties files, xml files, etc. in 
the /WEB-INF/classes directory for a Tomcat application. 

When you do this, you generally have the classes directory set as the output 
directory, so that Tomcat can pick up and dynamically load changed classes on 
the fly.

When the output directory is set to /WEB-INF/classes directory, the scrubbing 
deletes property files, and xml files as well as the java class files.

If you must scrub more than just java .class files, then at least can you make 
it configurable to be able to exclude file extensions from being scrubbed.

George L. Smith
Pinnacle Corporation
Comment 1 Philipe Mulet CLA 2003-01-30 10:53:17 EST
In recent integration builds (since M4), you can turn off the cleaning behavior 
and get what I think you want.

See Preferences>Java>Compiler>Other>Allow to clean output folder...

Is it ok to close ?
Comment 2 George L. Smith CLA 2003-01-31 18:13:19 EST
Thanks for the comment, and I haven't tried builds beyond M4. I am running M4 
and the existing M4 behavior that allows me to turn off the scrubbing, doesn't 
handle the problem. It turns off the scrubbing and then the project doesn't 
compile correctly. So if this is the same solution, then no it does not solve 
the problem.
Comment 3 Kent Johnson CLA 2003-02-07 15:46:26 EST
When you say the project doesn't compile correctly, what problems are you 
seeing?

Can you reproduce any of these problems in the latest integration build?
Comment 4 Kent Johnson CLA 2003-02-12 16:38:09 EST
Closing until we get repeatable steps in the latest integration build.