[osmosis-dev] Checkstyle
marcus.wolschon at googlemail.com
marcus.wolschon at googlemail.com
Wed Jan 28 13:23:35 GMT 2009
On Wed, 28 Jan 2009 23:42:29 +1100, Brett Henderson <brett at bretth.com>
wrote:
> marcus.wolschon at googlemail.com wrote:
>> You can export the eclipse formating-rules and put them into the
project.
>> The same goes for the checkstyle-rules as checked by eclipse while
>> coding.
>> I recomment extending line-length to >80 characters but to leave it in,
>> cyclomatic complexity, variable/argument/constant-naming and
access-level
>> checks.
>>
> Do you mean you can export the eclipse rules and have them used by
> checkstyle in some way, or just that we can share formatting rules
> between eclipse environments?
Both. Eclipse has a checkstyle-plugin too that marks things while
you are coding. It can reference an xml-file with the checkstyle-rules
on a per project basis.
The eclipse code-formating and code-templates can be exported
and imported to/from an xml-file that can be stored in the project
itself. This way you can have per-project templates and everyone
working on a project has the same code-style and templates.
> Either way it sounds good. Then we can
> start a potentially lengthy discussion on code formatting rules :-) To
> be honest I haven't changed the eclipse defaults much, mainly just a few
> tweaks such as inserting extra blank lines between methods.
My usual set of rules in not much different. Just the sun-checks
weakened to a state that is actually usable. (In the days of wide-screen
high-res LCDs forcing an 80-column display is just nonsense.)
Marcus
More information about the osmosis-dev
mailing list