Plugins (1000)


Training and Consulting (67)


Eclipse Summit Europe 2009


EPIC Poll

What is your favourite developer portal?

[ Results | Polls ]

Votes: 598
Comments: 0

EPIC has moved! The content of this site has been frozen and placed in a Read-Only State. Check out our new Eclipse Marketplace site. Logins to this site have been disabled.


Category: Plugin Directory / Source Code Analyzer / Checkstyle Plug-in

This listing has moved and is Out of Date. Please view the most up to date listing here:
http://marketplace.eclipse.org/content/checkstyle-plug

Checkstyle Plug-in 
Rate this plugin | Report broken link | Details | Comments (317)

Rating: 8.8 (2583 Votes) | hits: 3
Checkstyle Plug-in

Version: 5.0.0
Support Eclipse Version: 3.2.x/3.3.x/3.4.x/3.5.x
License: Free LGPL
Development Status: Production/Stable
Company: David Schneider, Lars Koedderitzsch
Plugin home pageHome Page
Plugin SupportPlugin Support
Discussion ForumsDiscussion Forum
Update Site URL: http://eclipse-cs.sf.net/update/

The eclipse-cs Checkstyle plug-in integrates the well-known source code analyzer Checkstyle into today's leading IDE - Eclipse. Checkstyle is a development tool to help you ensure that your Java code adheres to a set of coding standards. Checkstyle does this by inspecting your Java source code and pointing out items that deviate from a defined set of coding rules. With the Checkstyle Eclipse plug-in your code is constantly inspected for problems. Within the Eclipse workbench you are notified of problems via the Eclipse Problems View and source code annotations just as you would see with compiler errors or warnings. A comfortable Check Configuration Editor helps you create and maintain your audit rule configurations. Using filters and file sets you are able to define which files get checked and which don't.
Added on: 26-May-2005 | Updated: 29-Jun-2009




Last 10 Comments


User: outsideRating: 102010-02-02 09:13:13
PAN


User: outsideRating: 102010-01-26 10:58:32
It's Great


User: outsideRating: 62010-01-24 14:25:01
really helpful, but a) there definitely should be a quick way to find out about the rationale behind each rule / violation: i click on a marker and have the option "show rule rationale" (orsomething equivalent in the violation view) instead of having to remember the rule name, go to the preferences and browse until i find the respective rule. a) there should be a quicker way to enable/disable certain rules, either directly from the editor, or in the violation view.


User: outsideRating: 82010-01-24 07:28:02
So far I've really like what this has to offer, except for a few things: - It would be nice to be able to select a Checkstyle Problem and go to the rule that is triggering this problem, so that I could disable things I don't think are problems. - I'm using the Java Formatter and Clean Up on save which is putting whitespace in my Javadocs, which Checkstyle is complaining about, so I'd like to be able to temporarily ignore/hide the "line has trailling spaces" warnings. - The ignore parameter hidding member variable (field) on setter methods doesn't seem to be working for me and I couldn't find documetation that I could use to understand how to use the ignore filter to do this instead. Thank you for this tool


User: outsideRating: 102010-01-22 04:45:20
Quality code master !


User: outsideRating: 102010-01-02 07:08:57
This plugin is great. When I had to upgrade to version 5, there were some upgrade isssues. I missed it when I did not had it. Now I have it, and I am am happy. This plugin is a must.


User: outsideRating: 12009-12-21 00:08:44
QUIT FUCKING WITH MY STYLE.


User: outsideRating: 102009-12-10 17:38:42
This is a great plug-in, you have nailed the implementation of checkstyle and allowed us to easily adopt / customize a template to suite our needs. The only thing I would add is a fuction to print the template to pdf ...


User: outsideRating: 102009-12-10 11:01:54
Extremely helpful to enforce a common style and usage in a team of programmers.


User: outsideRating: 102009-12-07 07:33:21
Great, you brilliant minds! Now I'm more concerned with codeStyle than with actual CODE!!!