Roman Ivanov
Roman Ivanov
Workaround is multiline comment `/* bla bla violation bla*/`
Yes, we kind of make word so special , that users should not use in single line comments `//` . We are ready for this. It is better than missing...
fix is merged. further improvements in test infrastructure will be defined at https://github.com/checkstyle/checkstyle/issues/15643
@Alterant-zz , thanks a lot for report, please strictly follow issue template , no "..." we need fully compile-able java class , not a chunk of it.
Line 53, uhh, can you put `// violation ` comment on line 53 to know exact place. It will be good if you cut unrelated code to just be compile...
we usually place "bug" label after fix (as this label is for release notes)
@MohanadKh03 , thanks a lot for help, you are always welcome to fix any issues. We highly recommend (but not a mandatory requirement) for new contributors to finish one issue...
Better to discuss in PR, see you in PR
please read https://checkstyle.org/report_issue.html#How_to_request_new_Check.2FModule.3F pay attention to example link. to approve issue we need to see design with all names and behavior on some basic code.
xpath is updated to avoid false positive of XpathMatch ``` $ javac Test.java $ cat Test.java public class Test { public void plugin() { int a = 5; // violation...