findbugs

FindBugs offers this granular control with exclude and include filters .

FindBugs提供了这种细化的控制，可以排除或者包含过滤器。

Let 's take a look at how to use FindBugs from an Ant build script .

让我们看一下如何在Ant编译脚本中使用FindBugs。

FindBugs is an open source static analysis tool that looks for likely bug patterns in code .

FindBugs就是一个能够查找代码中可能的缺陷模式的开源静态分析工具。

The optional attribute output specifies the output format that FindBugs will use for its results .

可选属性output指定FindBugs的结果使用的输出格式。

In the first article in this series , I showed you how to set up and execute FindBugs .

在本系统的第一篇文章中，我展示了如何设置和执行FindBugs。

Because this article is about FindBugs , we 'll use FindBugs to solve the problem .

因为本文讨论的是FindBugs，所以我们将用FindBugs解决这个问题。

Tools like FindBugs can often turn into political weapons used to bludgeon teams or individuals .

像FindBugs这样的工具通常会成为用于敲打团队或者个人的政治武器。

One of the first questions that 's often asked is why would I want to add FindBugs into my build process ?

经常问到的第一个问题是为什么要将FindBugs加入到编译过程中？

See the FindBugs manual for more details .

更多细节请参阅FindBugs手册。

I want to reiterate some of the sentiment expressed in one of the FindBugs papers .

我想重申在一篇FindBugs论文中表述的一些观点。

Tools like FindBugs certainly won 't find all the bugs , but they 'll help find some of them .

像FindBugs这样的工具当然不会找出所有的缺陷，但是它们会帮助找出其中的部分。

All bytecode scanning detectors are based on the visitor pattern , which FindBugs implements .

所有字节码扫描检测器都基于visitor模式，FindBugs实现了这个模式。

Findbugs is a popular open source tool that performs static analysis on Java ™ byte code to find common programming errors .

Findbugs是一个流行的开放源代码工具，它对Java™字节代码执行静态分析以查找常见编程错误。

FindBugs is a truly impressive tool & it manages to find real bugs , nearly all the time .

FindBugs确实是一种不寻常的工具，它几乎可以在任何时间找出实际的bug。

Fortunately , FindBugs has a number of detectors that can help identify incorrectly synchronized classes .

幸运的是，FindBugs拥有大量的检测器，它们可以帮助识别错误同步的类。

As FindBugs analyzes a class , it will call the visit ( Code ) method when the contents of a method are walked .

在FindBugs分析类时，它会在分析方法内容时调用visit（Code）方法。

Static Analysis tools such as FindBugs , IntelliJ , Checkstyle and PMD are widely used in Java development .

诸如FindBugs、IntelliJ、Checkstyle和PMD这样的静态分析工具在Java开发中得到了广泛应用。

For example FindBugs and IntelliJ both define their own annotations to indicate when a method may return null .

比如FindBugs和IntelliJ都定义了自己的注解，以表示方法何时返回null。

They 're valuable tools that can find real problems , and FindBugs is one of the better ones for eliminating false positives .

它们是有用的工具，可以找出真正的问题，而FindBugs是在消除误检方面做得最好的工具。

FindBugs detects a number of questionable finalizer constructs , such as

FindBugs检测很多有问题的finalizer构造，如

Let 's rehash some past advice and see how FindBugs can help detect when you fail to follow it .

让我们以新方式重复前面的一些建议，并了解在没有遵守这些建议时，FindBugs如何帮助检测。

Exclude and include filters are currently supported only in the command-line or Ant versions of FindBugs .

当前只有用命令行或者Ant启动的FindBugs中支持排除和包含过滤器。

Next , I browsed the FindBugs source code looking for a detector I thought was similar to the one I wanted to write .

其次，查看FindBugs源代码以查找类似于我要编写的检测器类似的检测器。

PMD is a static Java source code analysis tool , similar in concept to Checkstyle , FindBugs and Coverity .

PMD是一个静态Java源码分析工具，从概念上讲与Checkstyle，FindBugs和Coverity很相似。

But FindBugs is different & it uses bytecode analysis and a host of plug-in bug pattern detectors to find common bugs in code .

但是FindBugs不同，它利用字节码分析和很多内置的bug模式检测器来查找代码中的常见bug。

I encourage you to try some form of static analysis tool on your code , whether it 's FindBugs , PMD , or something else .

我鼓励读者对自己的代码试用静态分析工具，不管是FindBugs、PMD还是其他的。

Finding some now is better than your customers finding them later & especially when the cost of incorporating FindBugs into your build process is so low .

现在找出部分比客户在以后找到它们要好&特别是当将FindBugs结合到编译过程中的成本是如此低时。

Whether you 're new to FindBugs or already familiar with it , I encourage you to experiment with your own application-specific detectors .

不管是刚接触FindBugs还是已经熟悉它了，我鼓励您用自己的特定于应用程序的检测器进行试验。

In this installment , I 'll explain how FindBugs can help ensure that this design advice is followed in an existing codebase .

在这一期，我将解释FindBugs如何确保现有代码库遵循设计建议。

Where we differ from FindBugs is in the depth of analysis that we perform , and the number and type of defects that we can find .

我们同FindBugs的不同之处在于分析的深度，可发现缺限的数量和种类。