2

After migrating maven-checkstyle-plugin to SonarQube, I face some oddity how line feeds and tab chars are transfered.

Back in my Maven build I had the following substantial rules:

<module name="Checker">
  <property name="fileExtensions" value="java, xml"/>
  <!-- forbid dos/windows lf -->
  <module name="RegexpMultiline">
    <property name="format" value="\r\n" />
    <property name="message" value="Do not use Windows line endings."/>
  </module>
  <!-- forbid tab character -->
  <module name="FileTabCharacter">
    <property name="eachLine" value="true" />
  </module>
</module>

While checking the SonarQube report I don't see these violations, where they should be. What am I doing wrong here?

PS: SonarQube got this snippet as configured QG/QP.

Robert Heine
  • 1,820
  • 4
  • 29
  • 61
  • 1
    This is syntactically incorrect (missing `/>` in some places). That part of the problem? – barfuin Oct 13 '16 at 07:28
  • @ThomasJensen Sorry, edited the pasted text to remove some internal comments and left the file errorous. Thanks for hinting this. – Robert Heine Apr 18 '17 at 13:39

1 Answers1

-1

Your analysis is now based on the rules that are active in your SonarQube Quality Profile. You should re-create your rules in SonarQube.

G. Ann - SonarSource Team
  • 22,346
  • 4
  • 40
  • 76