I found that some Java issues are detected by sonarlint but not SonarQube analysis. Here is an example:
S4488 is found by sonarlint in eclipse because the controller is using bad spring annotation but when I submit the project to SonarQube, the report said the annotation is OK.The project is being analysed by default (Java) Sonar way and i check that the rule are present and active. (As i m a new user i can only upload one pic so i group the screen to single picture)
Is someone also hitting the same problem? I am not sure this is caused by rules are ignored in sonarqube or the code cannot be detected properly due to text / pattern problem.
Version Used: SonarQube developer Version18.104.22.168448, SonarJava 5.14 (build 18788)installed