We use the Checkstyle rule "Comment pattern matcher" to search for different markers in Java comments.
Unfortunately, the rule also searches in Javadoc comments, Sonar reports them as violations, too. It leads to problems in our CI environment. Our source code management system writes file history at the end of Java file, as Javadoc comment. If the developer used the pattern word while checking in the file to SCM then the pattern appears later in Javadoc comment section at the end of the file.
The bug-fix should limit the search scope of the rule "Comment pattern matcher" to only Java comments.