Sonar Methods should not be empty at the constructor
Question
I updated my Sonar to Version 5.1.2, and the issue Methods should not be empty appears on this code:
public User() {}
public User (String login) {
this.login = login;
}
It seems to be a bug. Am I right? Because this didn't happen before.
2 answers
solution1
7 ACCPTED 2015-09-17 14:36:21
I found this jira, It's a Sonar's Bug.
solution2
0 2015-10-04 14:24:22
It really seems to be unexpected behavior. I think it was the ticket response above what caused it. I'm trying to talk to the developer to set the S1186 rule. If you want to follow:
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Empty ObjectFactory constructor is critical issue in Sonar
Sonar: Instance methods should not write to "static" fields
Sonar issue : Classes and methods that rely on the default system encoding should not be used
Is the Sonar rule for Spring '"@RequestMapping" methods should be "public"' accurate?
Java: Sonar compulsory constructor
Sonar alert : “private” methods that don't access instance data should be “static”
Java 8 stream fix Intermediate Stream methods should not be left unused sonar issue
Empty GroupID sonar eclipse
Sonar Violations of Unused methods in if statement
Sonar: Null pointers should not be dereferenced
Related Tags