FindBugs 在 GWT 项目的 Jenkins 中给出错误
我安装了 Jenkins 作为 CI 工具。我还安装了 findbugs 插件来查找潜在的错误。 (还有 checkstyle、pmd 等)。 我的项目是一个使用maven结构的gwt项目。 我在jenkins配置页面中编写了执行findbugs的目标。
clean package findbugs:findbugs
但我收到以下错误,并且没有从 findbugs 中得到任何结果。其他插件工作正常。
[INFO] Fork Value is true
[java] The following classes needed for analysis were missing:
[java] com.google.gwt.core.client.GWTBridge
[java] Missing classes: 2
[INFO] xmlOutput is false
FindBugs 有什么区别?我应该改变什么?
I installed Jenkins as CI tool. I installed also the findbugs plugin to find potential bugs. (Also checkstyle, pmd, etc.).
My Project is a gwt-project using maven structure.
I wrote the goals in jenkins configuration page to execute findbugs.
clean package findbugs:findbugs
But I am getting the following error and dont get any result from findbugs. The other plugins are working properly.
[INFO] Fork Value is true
[java] The following classes needed for analysis were missing:
[java] com.google.gwt.core.client.GWTBridge
[java] Missing classes: 2
[INFO] xmlOutput is false
What is the difference of FindBugs? What should I change?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这将在即将发布的 gwt-2.5.1 版本中得到修复,补丁位于此处 http://gwt -code-reviews.appspot.com/1722803。
解决方法 - 将 gwt-dev 添加到类路径 - https://groups.google.com/forum/?fromgroups=#!topic/google-web-toolkit-contributors/JQCU4mQWNX0
删除了该内容GWTridge 向我发出警告。
This will be fixed in the upcomping gwt-2.5.1 release and the patch is here http://gwt-code-reviews.appspot.com/1722803.
Workaround - adding gwt-dev to the classpath - https://groups.google.com/forum/?fromgroups=#!topic/google-web-toolkit-contributors/JQCU4mQWNX0
That removed that GWTBridge warning for me.
我认为这是因为 findbugs 在 JAR 中看到了 GWT 源代码。我们在 findbugs-maven-plugin 配置中使用
com.mycompany.
解决了这个问题。I think this is because findbugs sees the GWT sources in the JARs. We've worked around this using
<onlyAnalyze>com.mycompany.</onlyAnalyze>
in the findbugs-maven-plugin configuration.