Bug 250595 - Pattern suggestion
Summary: Pattern suggestion
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-13 00:01 EDT by Andrew CLA
Modified: 2009-02-08 12:12 EST (History)
2 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 Andrew CLA 2008-10-13 00:01:05 EDT 
I have a suggestion for the project:  A code analyzer could be adopted to determine patterns which could be used to simplify and strengthen the design.  For example, a long switch statement could suggest an appropriate place to employ polymorphism, or a class that is only ever instantiated once at a given time, could suggest an appropriate place for a factory.  The enhancement should then provide facilities for refactoring if a pattern is to be used.
Comment 1 Kevin McGuire CLA 2008-10-29 15:48:31 EDT 
Would be cool indeed.
Comment 2 Dani Megert CLA 2009-02-08 12:12:34 EST 
More useful than just a pattern would be access to either the Java mode or even the AST (which could cause performance issues though).

If it is a problem reporting tool then it's better hosted in JDT Core. If it would also fix the issue we could provide it as Clean Up in JDT UI.