blocks|key|5372914|text|这可能是不可能的。您可以使用数据挖掘任务并进行一些特殊处理。http://findbugs.sourceforge.net/manual/datamining.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5372915|entityMap|0|LINK|mutability|MUTABLE|url|http://findbugs.sourceforge.net/manual/datamining.html^0|U|1I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

That may not be possible. You can use data mining task and do some special handling. <a href="http://findbugs.sourceforge.net/manual/datamining.html" rel="nofollow">http://findbugs.sourceforge.net/manual/datamining.html</a>

blocks|key|1332573|text|这可能有点过头了，但我仍然将其添加为答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1332574|为此，您可以使用sonar。Sonar是一个测量和跟踪代码质量的免费平台。它包含了findbugs指标。|offset|length|1332575|它有Build+Breaker+Plugin，这会在某些情况下破坏你的构建。|1332576|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sonarsource.org/|1|http://docs.codehaus.org/display/SONAR/Build%2BBreaker^0|0|8|5|0|0|2|K|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

This may go a bit too far, but I'm adding it as an answer none the less.

You can use <a href="http://www.sonarsource.org/" rel="nofollow">sonar</a> for that. Sonar is a free platform to measure and track code quality. It has findbugs metrics included.

It has the <a href="http://docs.codehaus.org/display/SONAR/Build+Breaker" rel="nofollow">Build Breaker Plugin</a>, which will break your build on certain conditions.

blocks|key|1332752|text|You+need+to+write+a+custom+ant+task，派生自Ant的Task基类，它添加了一个日志侦听器，该侦听器设置属性并在之后删除自身。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1332753|日志监听器需要识别findBugs何时在记录日志，辨别哪条日志消息列出了错误的数量，解析该行，设置属性并将其自身从日志监听器集中删除。|1332754|一旦有了这个任务you+need+to+also+write+a+new+condition，Ant就不会附带数字比较条件。然后，您可以在失败任务中使用自定义条件，就像任何其他条件一样。|1332755|<findBugCountListener+prefix="findbugs.count"/>
<findBugs+...>
</findBugs>
<fail>
++<condition+property="allupper">
++++<and>
++++++<isset+property="findbugs.count"/>
++++++<greaterThan+value="${findbugs.count}"+limit="522"/>
++++</and>
++</condition>
</fail>|code-block|syntax|javascript|1332756|理想情况下，您的侦听器将设置一个带有bug数量的Ant属性。然后，如果bug数量太多，您可以使用AntContrib的Assert任务抛出构建异常。|1332757|是的，与简单地配置几个标记相比，这是更多的手动工作，但至少可以使用Ant加载自定义扩展。它不像Ant是在明确了解findBugs插件的情况下编写的(它自然需要在以后编写)。|1332758|另一种选择是找到findBugs+ANT插件的源代码，并假设它具有允许合法修改的许可证，修改ANT插件以具有新的“附加”属性setCount="propName"，然后在现有的findBugs+ANT插件中捕获和设置该属性。|1332759|entityMap|0|LINK|mutability|MUTABLE|url|http://ant.apache.org/manual/tutorial-writing-tasks.html|1|http://ant.apache.org/manual/Types/custom-programming.html#customconditions^0|17|4|0|Z|0|0|0|8|12|1|0|0|0|0|1Q|J|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|J|3|K|5|L|7|1F|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1H|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

<a href="http://ant.apache.org/manual/tutorial-writing-tasks.html" rel="nofollow">You need to write a custom ant task</a>, deriving from Ant's <code>Task</code> base class, which adds a log listener that sets a property and removes itself afterwards. The custom task will fetch the current <a href="http://api.dpml.net/ant/1.6.5/org/apache/tools/ant/Project.html" rel="nofollow"><code>Project</code> and add the log listener via addLogListener(...)</a>.

The log listener needs to identify when findBugs is logging, discern which log message is the one that lists the number of bugs, parse that line, set the property and remove itself from the set of log listeners.

Once you have that task, <a href="http://ant.apache.org/manual/Types/custom-programming.html#customconditions" rel="nofollow">you need to also write a new condition</a>, as Ant doesn't ship with a numeric comparison condition. Then you can use your custom condition in the fail task, like any other condition.

<pre><code>&lt;findBugCountListener prefix="findbugs.count"/&gt;
&lt;findBugs ...&gt;
&lt;/findBugs&gt;
&lt;fail&gt;
 &lt;condition property="allupper"&gt;
 &lt;and&gt;
 &lt;isset property="findbugs.count"/&gt;
 &lt;greaterThan value="${findbugs.count}" limit="522"/&gt;
 &lt;/and&gt;
 &lt;/condition&gt;
&lt;/fail&gt;
</code></pre>

Ideally your listener will then set an Ant property, with the number of bugs. You can then use AntContrib's Assert task to throw a build exception if the number of bugs is too high.

Yes, it is more manual work than simply configuring a few tags, but at least it is possible with Ant due to it's ability to load custom extensions. It isn't like Ant was written with explicit knowledge of the findBugs plugin (which naturally had to be written afterwards).

Another alternative is to find the source code of the findBugs ANT plugin, and assuming it has a license that allows legal modification, modify the ANT plugin to have a new "additional" property, <code>setCount="propName"</code> and then capture and set the property within the existing findBugs ANT plugin.

blocks|key|5373137|text|这是一个相当老的问题，但可能对其他人有用:有一种相当简单的方法来实现所需的行为，方法是设置findbugs任务的warningsProperty属性，然后让fail检查该属性值：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5373138|<findbugs+...+warningsProperty="findbugs.warnings">
++...
</findbugs>
<fail>
++<condition><istrue+value="${findbugs.warnings}"/></condition>
</fail>|code-block|syntax|javascript|5373139|(不用说，findbugs现在已经被抛弃了，但spotbugs是它的继任者。)|5373140|entityMap|0|LINK|mutability|MUTABLE|url|https://spotbugs.github.io/^0|19|8|1K|G|26|4|0|0|N|8|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Quite an old question, but maybe this is useful for someone else: There is a rather simple way to achieve the desired behavior by setting the <code>warningsProperty</code> attribute of the <code>findbugs</code> task and afterwards letting <code>fail</code> check for the property's value:

<pre><code>&lt;findbugs ... warningsProperty="findbugs.warnings"&gt;
 ...
&lt;/findbugs&gt;
&lt;fail&gt;
 &lt;condition&gt;&lt;istrue value="${findbugs.warnings}"/&gt;&lt;/condition&gt;
&lt;/fail&gt;
</code></pre>

(Needless to say that findbugs is abandoned now, but there is <a href="https://spotbugs.github.io/" rel="nofollow noreferrer">spotbugs</a> as a successor.)

I want to start findBugs on existing project (on command line there are currently 522 bugs).

How can I set in the ant file (under findbugs target) the option to fail the build if there are more than 522 bugs found?

I want to actually fail the ant build and not to understanf it manually from the output report.

Thanks.

How to fail my Ant build if findBugs target find bugs

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我想在现有的项目上启动findBugs (在命令行上，目前有522个bug)。如果发现超过522个bug，我如何在ant文件中(在findbugs目标下)设置使构建失败的选项？我希望ant构建实际上失败，而不是从输出报告中手动理解它。谢谢。

问如果findBugs目标发现错误，如何使我的Ant构建失败
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如果findBugs目标发现错误，如何使我的Ant构建失败EN