-
Notifications
You must be signed in to change notification settings - Fork 5
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
no benefit in using guardlog. #23
Conversation
jdrueckert commented on pr: MovingBlocks/Terasology#5154 that the rule is not really beneficial and better remove the rule than suppress it.
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com> squash later Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
Will be discussed in our next reviver meeting (tomorrow, Sunday 7PM UTC) |
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
we decided yesterday to keep the rule. |
There's an open issue on PMD regarding the |
Let's temporarily exclude the rule but with a TODO to reinclude it once the PMD issue (link it) is fixed. |
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
@@ -7,7 +7,6 @@ | |||
Terasology PMD ruleset | |||
</description> | |||
<exclude-pattern>.*/org.terasology.protobuf/.*</exclude-pattern> | |||
<!-- inline <rule ref="rulesets/java/basic.xml"/> --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we removing these comments?
If the usage of suppliers sufficiently fixes the findings such that PMD doesn't report them anymore despite the open PMD bug, maybe we don't need this after all. |
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
especially take out pmd guardlog suppresses. fix part of them in a catch even if not necessary from a performance point of view. and create a pull request towards teraconfig to not use the guardlog rule any more: MovingBlocks/TeraConfig#23 Co-authored-by: jdrueckert <jd.rueckert@googlemail.com>
jdrueckert commented on pr: MovingBlocks/Terasology#5154 that the rule is not really beneficial and better remove the rule than suppress it.
as well remove the not any more necessary comments.