You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assume you have a checkstyle configuration as described in [1], also checking pom.xml files in the root directory of the project, then currently those errors (on the module root) will not be shown by checkstyle in Eclipse, but reported by checkstyle run from Maven.
It is possible to open the project local settings for checkstyle and select the java-sources-checkstyle-check resource set and untick "files outside source directories". However this has to be done on each and every desktop for each and every project.
@ctron hallo Jens, nice to "see" you again here too... I know (from knowing you) that you know how this opensource thing 😃 works - as per #124 I wouldn't have the time to look into and fix this issue, but if you could raise a PR which fixes, I can (now) promise that we can get it merged and released (#123) ... looking forward to your contributions! 😈
Assume you have a checkstyle configuration as described in [1], also checking
pom.xml
files in the root directory of the project, then currently those errors (on the module root) will not be shown by checkstyle in Eclipse, but reported by checkstyle run from Maven.It is possible to open the project local settings for checkstyle and select the
java-sources-checkstyle-check
resource set and untick "files outside source directories". However this has to be done on each and every desktop for each and every project.[1] https://vzurczak.wordpress.com/2016/11/28/checking-root-resources-with-checkstyle-and-maven/
The text was updated successfully, but these errors were encountered: