Bug 48428 - Customized rules in compilation
Summary: Customized rules in compilation
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: 3.0 M6   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-10 14:06 EST by Lance Zhang CLA
Modified: 2003-12-16 07:58 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lance Zhang CLA 2003-12-10 14:06:30 EST
I am trying to looking into a solution that can detect some errors or faults in 
Java Eclipse development environment. Some of those errors are company 
specified. I found that Eclipse had certain rules defined in Java compliation 
in the perference view. But, can you add some interface to let the user to 
define their own rules for compilation and the condition to enable those rules 
by certain ways? (Enable or Disable, Warning or Error)

I found there was a tool call PMD. The PMD even has a Eclipse plugin, but I 
think it is doing a lot of duplicate work, which the JDT has already done.
Comment 1 Philipe Mulet CLA 2003-12-11 00:57:03 EST
These extra diagnosis are built in the Eclipse compiler. But you could write 
your own builder tool to diagnose further issues. Typically you would use the 
DOM AST API so as to get your hands on a resolved AST, and from there you could 
generate markers.

There is no mechanism available to grow the built-in compiler which we wanted 
to protect against API freezing. The DOM AST delivers somewhat equivalent 
technology.
Comment 2 Philipe Mulet CLA 2003-12-11 00:57:16 EST
Ok to close ?
Comment 3 Lance Zhang CLA 2003-12-11 09:29:46 EST
OK, I will try to build my own.

thanks/Lance