Bug 357924 - [clean up] Allow disable clean-up on some classes
Summary: [clean up] Allow disable clean-up on some classes
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-16 07:25 EDT by Martin Beranek CLA
Modified: 2011-09-16 12:38 EDT (History)
4 users (show)

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 Martin Beranek CLA 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 CLA 2011-09-16 12:03:11 EDT 
Markus, whats your take on this?
Comment 2 Dani Megert CLA 2011-09-16 12:16:45 EDT 
*very* low priortiy
Comment 3 Markus Keller CLA 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).