Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 60822

Summary:	Reacting to Project > Clean...
Product:	[Eclipse Project] JDT	Reporter:	John Arthorne <john.arthorne>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	3.0 M9
Hardware:	PC
OS:	Windows 2000
Whiteboard:

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).

Comment 1 Philipe Mulet

2004-05-04 09:19:02 EDT

We should try to honour this protocol.

Comment 2 Kent Johnson

2004-05-04 13:34:30 EDT

Done.

Implemented clean in JavaBuilder to call BatchImageBuilder.cleanOutputFolders.

Comment 3 Philipe Mulet

2004-05-05 05:16:50 EDT

Did you also remove existing Java problems ?

Comment 4 Philipe Mulet

2004-05-05 05:17:33 EDT

Did you also clear existing Java problems ?

Comment 5 Kent Johnson

2004-05-05 10:48:41 EDT

Yes, both Java problems & tasks were removed... they will be recreated during 
the next build.

Comment 6 Olivier Thomann

2004-05-18 13:37:20 EDT

Verified in 200405180816