Michael Keppler
Michael Keppler
The mockito-junit-jupiter extension uses dependabot to upgrade its own dependencies. That's why it always requires the latest JUnit Jupiter version. This is bad for projects that want to use the...
The build of this project fails on checkstyle errors. The Eclipse plugins however don't have any Eclipse CS configuration. Therefore during editing new checkstyle failures are not reported and will...
Have you ever thought about a kind of filtering to exclude some files and folders from the refactorings? E.g. we have some generated code (from EMF, Xtext, etc.) and I...
The cleanup can be configured either in preferences or project specifically in the project properties of a java project. However, the enabled refactorings of the current cleanup profile are always...
If you use ArchUnit just for writing unit tests in your project, you will always fix the issues found by tests or edit the rules to eventually exclude a class...
Looks like this in the affected menus:
The Eclipse plugins are currently configured to use the Google checks, see for instance https://github.com/checkstyle/eclipse-cs/blob/master/net.sf.eclipsecs.core/.checkstyle. However, during a PR build, the (otherwise not referenced) configuration from https://github.com/checkstyle/eclipse-cs/blob/master/config/checkstyle_checks.xml is used. That...
I was going to fix some deprecations, but doing so I noticed that the code would get littered with more and more duplicated catch-clauses due to newly introduced exception types...
* remove lazy resolution of target files, which is not recommended at all (since every build might build against other dependencies then) * set compiler compliance to 11 * require...