will help you I'm not entirely sure why this does not work, but I had to get rid of the tag in the F# project file in order to get F# Formatting project to work on Travis (building using Mono) and the change I had to do looks like this (GitHub diff). Sorry for the lack of clarity - I probably copied this from some other project. The diff replaces the tag with:
Hope that helps Once your Eclipse project is associated to a remote SonarQube project, changing its name should have no impact (association is a dedicated metadata). By default when you try to associate an Eclipse project we use the project name to do the search. This is because we want to be independent from Maven and support any Eclipse project.
SonarQube fail to execute goal on empty instance "module already part of project"
will help you sub-modules should be properly deleted but for the sake of it you could check for ghost data under Settings - System - Bulk Deletion. You could also query the api/projects/index?subprojects=true WebService to check if somesubmodule appears somewhere.
MSBuild.SonarQube.Runner.exe EXECUTION FAILURE with "MSBUILD : error MSB1009: Project file does not exist."
Does that help Our .NET solution is compiling well from MSBUILD command line. We're using MSBuild.SonarQube.Runner.exe for Sonar Quality metrics which fails with message , I've solved this by bypassing FxCop rules on the project.
SonarQube 5.3 log: "Undefined method 'empty?' for nil:NilClass" error messages