blocks|key|1585422|text|更多的谷歌%2B实验，我终于想出了一种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1585423|检查http://findbugs.sourceforge.net/manual/filter.html下的Section+6。|offset|length|style|CODE|1585424|您需要创建自己的XML文件，其中包含所有自定义抑制。然后，您需要通过findbugs.exclude.filter让build.xml文件了解此文件|1585425|+<Match>
+++<Class+name="com.foobar.MyClass"+/>
+++<Method+name="someMethod"+/>
+++<Bug+pattern="DLS_DEAD_LOCAL_STORE"+/>
+</Match>|code-block|syntax|javascript|1585426|一旦该标记存在于@SuppressWarnings中，就不需要在方法中添加该标记。|1585427|希望这对某些人有帮助！|1585428|entityMap|0|LINK|mutability|MUTABLE|url|http://findbugs.sourceforge.net/manual/filter.html^0|0|1I|9|2|1E|0|0|Y|N|0|0|8|H|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@$D|14|E|15|1|16]]|A|$]]|$1|H|3|I|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1A|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

More Googling + Experimenting and I finally figured out a way to do this. 

Check <code>Section 6</code> under <a href="http://findbugs.sourceforge.net/manual/filter.html" rel="noreferrer">http://findbugs.sourceforge.net/manual/filter.html</a> .

You need to create your own XML file with all the custom supressions in there.
You'll then need let build.xml file know about this file via <code>findbugs.exclude.filter</code>

<pre><code> &lt;Match&gt;
 &lt;Class name="com.foobar.MyClass" /&gt;
 &lt;Method name="someMethod" /&gt;
 &lt;Bug pattern="DLS_DEAD_LOCAL_STORE" /&gt;
 &lt;/Match&gt;
</code></pre>

No need to add the <code>@SuppressWarnings</code> tag in the method once this is there in the XML.

Hope this helps someone!

blocks|key|1585454|text|我在这段代码中也遇到了同样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1585455|@Test
public+void+testSomething()+{

++++@SuppressWarnings("unused")
++++@SuppressFBWarnings(value+=+"DLS_DEAD_LOCAL_STORE")
++++final+SomeMockClass+mock+=+new+SomeMockClass();
++++...
++++}
}|code-block|syntax|javascript|1585456|@SuppressFBWarnings在这里不起作用。|offset|length|style|CODE|1585457|这里的解决方案是将@SuppressFBWarnings上移到方法级别：|1585458|@Test
@SuppressFBWarnings(value+=+"DLS_DEAD_LOCAL_STORE")
public+void+testSomething()+{

++++@SuppressWarnings("unused")
++++final+SomeMockClass+mock+=+new+SomeMockClass();
++++...
++++}
}|1585459|我喜欢保持这些注释的范围尽可能小，这样它们就不会隐藏真正的问题。这里似乎有必要对整个方法进行注释。|1585460|entityMap^0|0|0|0|J|0|9|J|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$I|10|J|11|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

I just had the same problem with this code:

<pre><code>@Test
public void testSomething() {

 @SuppressWarnings("unused")
 @SuppressFBWarnings(value = "DLS_DEAD_LOCAL_STORE")
 final SomeMockClass mock = new SomeMockClass();
 ...
 }
}
</code></pre>

The <code>@SuppressFBWarnings</code> does not work here.

The solution here was to move the <code>@SuppressFBWarnings</code> up to the method level:

<pre><code>@Test
@SuppressFBWarnings(value = "DLS_DEAD_LOCAL_STORE")
public void testSomething() {

 @SuppressWarnings("unused")
 final SomeMockClass mock = new SomeMockClass();
 ...
 }
}
</code></pre>

I like to keep the scope of these annotations as small as possible, so they don't suppress real problems. Here it seems to be necessary to annotate the whole method.

blocks|key|1585467|text|显然，Sun/Oracle的As+explained+in+FindBugs+documentation编译器经常为final局部变量生成死存储。这些DLS_DEAD_LOCAL_STORE警告不能轻易抑制。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1585468|但是，我不确定为什么XML过滤器可以工作(就像在公认的答案中一样)。|1585469|entityMap|0|LINK|mutability|MUTABLE|url|http://findbugs.sourceforge.net/bugDescriptions.html#DLS_DEAD_LOCAL_STORE^0|1M|5|E|12|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

<a href="http://findbugs.sourceforge.net/bugDescriptions.html#DLS_DEAD_LOCAL_STORE" rel="nofollow">As explained in FindBugs documentation</a>, apparently Sun/Oracle's javac compiler often generates dead stores for <code>final</code> local variables. These DLS_DEAD_LOCAL_STORE warnings cannot be easily suppressed.

Not sure why the XML filter does work (as in the accepted answer), though.

I'm trying to eliminate a false positive for DLS_DEAD_LOCAL_STORE

Here's what I have tried so far:

<pre><code>@SuppressWarnings("DLS_DEAD_LOCAL_STORE")
</code></pre>

<code>@edu.umd.cs.findbugs.annotations.SuppressWarnings("DLS_DEAD_LOCAL_STORE")</code>

(based on <a href="https://stackoverflow.com/questions/10884606/suppresswarnings-not-working-on-findbugs">SuppressWarnings not working on FindBugs</a>)

<code>@edu.umd.cs.findbugs.annotations.SuppressWarnings(value = "DLS_DEAD_LOCAL_STORE", justification = "please go away")</code>

based on <a href="http://osdir.com/ml/java-findbugs-general/2010-06/msg00017.html" rel="noreferrer">http://osdir.com/ml/java-findbugs-general/2010-06/msg00017.html</a>

But none of the options is helping. Please advice.
Using Eclipse Indigo.

DLS_DEAD_LOCAL_STORE SuppressWarnings FindBugs false positive

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在试着排除DLS_DEAD_LOCAL_STORE的假阳性这是我到目前为止尝试过的方法：@SuppressWarnings("DLS_DEAD_LOCAL_STORE")@edu.umd.cs.findbugs.annotations.SuppressWarnings("DLS_DEAD_LOCAL_STORE")(...

问DLS_DEAD_LOCAL_STORE SuppressWarnings FindBugs误报
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问DLS_DEAD_LOCAL_STORE SuppressWarnings FindBugs误报EN