Michael Keppler

I referenced the wrong issue in my commit, therefore re-opening.

Seems reasonable, even if it puts additional effort on the original reporters. The benefit of this approach is a very healthy cleaning of no more reproducable or nor more important...

If test folders shall be ignored completely, wouldn't it be more useful to configure a [BeforeExecutionExclusionFileFilter](https://checkstyle.org/config_filefilters.html#BeforeExecutionExclusionFileFilter)? My understanding was that this one completely avoids matching files from being processed, while...

The Eclipse Checkstyle plugin doesn't differentiate between main sources and test sources (and never did, as far as I know). So it should have been scanning the test sources also...

Can someone explain why the build failed? It looks like it checks all changed files for checkstyle violations. If so, the current EclipseCS sources have around 1400 violations, therefore any...

This needs to be rebased after #351 has been fixed and the resulting checkstyle issues are also fixed.

I'm also in favor of rejecting this. The problem here is not that checkstyle is not invoked automatically anymore, but that the automatic build is disabled. And if that was...

Version changes of the EclipseCS plugin are yet another different story. The solution for that would be: * When running any EclipseCS analysis, store the current version number in the...

You probably need to edit your configuration file. 8.26 has compatibility breaking changes (and some of the versions before, too). See also https://github.com/checkstyle/eclipse-cs/issues/190. I would copy the remote config to...

It requires Java 11 to run itself, you can still compile code with older Java versions fine. Nevertheless, 1.7.0 is the highest version that I can use to build this...