25 lines
1.2 KiB
Plaintext
25 lines
1.2 KiB
Plaintext
=== on 7 Aug 2013, 16:52:06 Freddy Mallet wrote:
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARJAVA-272
|
|
|
|
=== on 14 Aug 2013, 07:53:48 Dinesh Bolkensteyn wrote:
|
|
We will generate false positives if overriding is used to change the super class method visibility.
|
|
|
|
=== on 14 Aug 2013, 08:38:55 Dinesh Bolkensteyn wrote:
|
|
We also generate false positives when Javadoc is added to the method.
|
|
|
|
=== on 19 Aug 2013, 13:08:28 Freddy Mallet wrote:
|
|
\[~dinesh.bolkensteyn] you're right for the first case but I disagree for the second one. Indeed overriding a method just to "fix" the javadoc, simply means that the javadoc of the super method is incorrect and should be updated.
|
|
|
|
=== on 21 Oct 2013, 16:25:56 Freddy Mallet wrote:
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3190 for Flex
|
|
|
|
=== on 4 Aug 2015, 19:31:25 Ann Campbell wrote:
|
|
I've mapped this to FxCop's RemoveEmptyFinalizers, [~tamas.vajk] but it only covers part of the scope: empty finalizers not covered here.
|
|
|
|
=== on 5 Aug 2015, 13:08:04 Tamas Vajk wrote:
|
|
\[~ann.campbell.2] To me this rule has nothing to do with empty finalizers.
|
|
|
|
=== on 5 Aug 2015, 16:03:16 Ann Campbell wrote:
|
|
agreed [~tamas.vajk]. The FxCop version covers both empty finalizers and finalizers that simply call base
|
|
|