没有适用于组件的DSM数据(Gradle Multi-Project) [英] No DSM data available for the component (Gradle Multi-Project)

问题描述

我刚刚从一个非常老的2.14版本升级到了Sonarqube 5.

I have just upgraded to Sonarqube 5 (from a very old 2.14).

当构建一个(新的)项目(多项目gradle构建，使用gradle 2.3-rc-3 )时，构建成功，并且在声纳控制台上我可以看到违反代码的行为.

When building a (new) project (multi-project gradle build, with gradle 2.3-rc-3), the build is successful and I see code violations ok on the sonar console.

当我点击设计"链接时，我得到了

When I click on the Design link, I get

该组件没有可用的DSM数据

寻找类似的问题/答案后，我检查了 ./build/tmp/sonarRunner/sonar-project.properties ，其中包含< project> .sonar.binaries 看起来正确的条目.

After looking for similar questions/answers, I have checked ./build/tmp/sonarRunner/sonar-project.properties and it contains <project>.sonar.binaries entries which look correct.

更新:

我刚刚尝试了全新的5.0安装；同样的结果.因此，我安装了4.5.2(又一个新的，干净的数据库)，它可以正常工作，因此看来这只是5.0的问题.

I just tried with a clean 5.0 install; same result. So I installed 4.5.2 (again a new, clean, db) and it works fine, so it looks like it's an issue with 5.0 only.

我正在通过此分支用...来构建spring-amqp ...

I am building spring-amqp from this branch with...

./gradlew build sonarRunner -Dsonar.host.url=http://xxxxx:9000 \ 
  -Dsonar.jdbc.url=jdbc:oracle:thin:@xxxxx:1521/XE \
  -Dsonar.jdbc.username=xxxxx -Dsonar.jdbc.password=xxxxx 

推荐答案

由于在，如果根本没有依赖项，则不会显示DSM，这在非Maven项目中确实存在问题，因为您无法直接从根项目中进行更底层的钻取.

Because of the optimization done on SONAR-5672, the DSM is not displayed when there's no dependency at all - which is indeed problematic on non-Maven projects because you can't drilldown on lower levels directly from the root project.

我们将通过 SONAR-6176 在5.1中修复此问题.

We'll fix this in 5.1 with SONAR-6176.

这篇关于没有适用于组件的DSM数据(Gradle Multi-Project)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！