-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EC4][Java] Rule is not applicable to Java #233
Comments
I agree that this rule should be discussed, it seems not revelant in Java. And I no longer see the rule in the latest version of best practices repo/book? Resources: |
|
Is it is not applicable for Java at all. and I almost freak out after I saw that the number of issues of our project have increased from 10 to 310 from one day to another because of it, plus EC2 and EC75 :) |
Hi @cyChop, @utarwyn, @diyfr, @cvgaviao,
Regarding EC2 rule, sorry, I don't agree. Please check refactoring work in issue #216 and associated PR #222. Regarding EC75, sorry again, I don't agree. For me it has been a good practice since a long time. Maybe now, with JVM upgrades, this rule could be deprecated. If it is, please could you give us documentation on this point, @cvgaviao, please ? But if you want to discuss about EC2 and EC75, please open a new issue for each, if you don't agree with my comments above. Thank you :p ! |
Hello @dedece35, you validate the test files said "COMPLIANT" with classic sonar rules to avoid conflict ? |
I think your mailbox trapped you, because I made an issue for each. I'll quote you on those issues and answer there. :) |
Could you give some reference in code to illustrate it, please ? |
Describe the bug
The rule "avoid global variables" is not applicable to Java.
The history: the first rules were inspired by web best practices, and transposed to other languages without analysis due to lack of time. This shows in the description of this rule, which shows JS.
Scope is not an issue in Java, and constants are a best practice for readability and memory optimization. EC4 is not applicable to Java and should be removed.
The text was updated successfully, but these errors were encountered: