Roman Ivanov
Roman Ivanov
It will be hard to help users if they do not share file and config to reproduce. Some cases could be simple but some hard to reproduce. @lkoe , can...
checkstyle 8.5 had guava `23.2-jre` https://github.com/checkstyle/checkstyle/blob/dbbd00f58fd36c7c23e24e6652076b735b8e7c0c/pom.xml#L274 we removed guava from api at 8.7 release - http://checkstyle.sourceforge.net/releasenotes.html#Release_8.7 removal of guava from internal packages is almost undoable, but we minimized its usage...
It works for me now.
Quick fix is possible only when you/plugin know how it works, it might for standard set of Checks but not third-party , this is why we have big future project...
Yes, meanwhile, eclipsecs can have their own quick fix logic.
core project use google groups for questions, it is used somehow (not very frequently), but in most cases users open github issues, or go to stackoverflow.
Such parse errors can happen if checkstyle executed on non compilable sources. If plugin is smart enough to distinguish draft file(non compile-able) and compiled it should run checkstyle only on...
@ManfredTremmel , do you know if this is possible to make use experience less scary ? nuance is that chekcstyle library do have problems with some java files on very...
Checkstyle should be executed only on compilable java source file, in other case behavior is not deterministic.
Let's do this after summer