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

Bug 357924

Summary:	[clean up] Allow disable clean-up on some classes
Product:	[Eclipse Project] JDT	Reporter:	Martin Beranek <martin>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	amj87.iitr, daniel_megert, markus.kell.r, remy.suen
Version:	3.8
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Martin Beranek

2011-09-16 07:25:02 EDT

Build Identifier: 20110615-0604

I thing, it is not good idea try to clean-up classes that are generated by various tools (e.g. hibernate's hbm2java). It will be nice to have opportunity to disable clean-op on some classes (e.g. by specifying package).

Reproducible: Always

Steps to Reproduce:
Menu: Source -> Clean Up ...

Comment 1 Ayushman Jain

2011-09-16 12:03:11 EDT

Markus, whats your take on this?

Comment 2 Dani Megert

2011-09-16 12:16:45 EDT

*very* low priortiy

Comment 3 Markus Keller

2011-09-16 12:38:40 EDT

You can already use the Package Explorer to select exactly the .java files, packages, or source folders you want to clean up. It's generally advisable to keep generated sources in a separate source folder, so selecting only your own code becomes trivial.

We have no plans to add a pattern language or something like that to disable certain packages, etc.

We could add an option to not clean up elements with an @javax.annotation.Generated annotation (off by default).