Description John Arthorne 2004-05-03 17:16:09 EDT

I20040427

When Project > Clean... is called, builders have an opportunity to discard
derived resources and remove other artifacts produced by builds.  The Java
builder should consider implementing this to discard .class flies (honoring the
"clean output folders" on full build preference) and discard problem markers.

Note: This is mainly a matter of user perception of the meaning of "clean" (the
expectation is that their class files will be deleted) - If the Java builder
does nothing on clean for 3.0, typical use cases will still work fine
(subsequent build after clean will be a full build and everything is rebuilt
from scratch).