Roland Auckenthaler wrote:
>In check coding/DeclarationOrderCheck.java line 130
> log(aAST, "declarationorder.method");
>but should be
> log(aAST, "declaration.order.method");
>Furthermore, the following files have some line-ending problems
>I'm using windows xp and these files were showing some problems with the
>(CR)LF at the end of the file which caused ant gump to fail on windows.
>I think on Linux/Unix environments there is no problem as it can cope
>with wrong line endings.
I'm on Linux, I hope some other developer with a Windows machine can fix
>I always thought about writing a checkstyle check for this problem but
>don't know how I can write a check outside of Treewalker (i.e. get hold
>of the actual raw java file). If people tell me what to look for (APIs).
>I'll write a check for it.
Such a check would be most welcome. Please have a look at
* the FileSetCheck interface
* the end of the "writing checks" documentation that explains how to
* Sourcecode of the NewLineAtEndOfFile check
Your code would be similar to the NewLineAtEndOfFile check, only that
you would have to check *all* linebreaks instead of only the last one.