简体   繁体   English

SonarQube由于findbugs和fbcontrib无法启动

[英]SonarQube fails to start due to findbugs and fbcontrib

I'm upgrading from Sonar 3.1.1 to SonarQube 4.0. 我正在从Sonar 3.1.1升级到SonarQube 4.0。 I have the sonar-fb-contrib-plugin-1.2.jar file in my extensions/plugins directory. 我的extensions / plugins目录中有sonar-fb-contrib-plugin-1.2.jar文件。 The startup fails with the following message: 启动失败,并显示以下消息:

2013.11.12 15:10:17 INFO  org.sonar.INFO  Install plugins done: 197 ms
2013.11.12 15:10:17 ERROR o.s.s.p.PlatformLifecycleListener  Fail to start server
org.sonar.api.utils.SonarException: Fail to extend the plugin findbugs for fbcontrib

My understanding is that findbugs comes bundled with SonarQube (I can see the jar file under bundled-plugins). 我的理解是,findbugs与SonarQube捆绑在一起(我可以在bundled-plugins下看到jar文件)。 I'm not sure what the problem is here - it doesn't look like this works out of the box as it did for 3.1.1 我不确定这里是什么问题-看起来像3.1.1那样开箱即用

I had a similar issue while upgrading from 3.6 to 3.7.3; 从3.6升级到3.7.3时,我遇到了类似的问题; the fbcontrib-plugin depends on the findbugs-plugin which is part of the sonar java-ecosystem. fbcontrib插件依赖于声纳java生态系统一部分的findbugs插件。

In this case it is safe (and documented , point 6) to take a backup of the database and of the extensions directory before updating; 在这种情况下,在更新之前对数据库和扩展目录进行备份是安全的(并记录在第6点中)。 then update and restart sonar having moved away any external contribution plugin, so that sonar can manage the update and come up back successfully. 然后更新并重新启动声纳,并移走了任何外部贡献插件,以便声纳可以管理更新并成功恢复。 Another good tip is to not overwrite new configuration files with the old ones, instead manually editing them to bring over the old settings. 另一个好的技巧是不要用旧的覆盖新的配置文件,而是手动编辑它们以覆盖旧的设置。

Then, add the plugins back and restart again; 然后,重新添加插件,然后再次重新启动; happy static analysis. 快乐的静态分析。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM