Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

Trouble shooting

  1. During gendarme analysis I get error message such as "Exception thrown looking for gendarme-report-PROJECT_NAME.xml report file"
    You might be using sonar dotnet plugins version 0.6 with maven dotent plugins 0.5 . Try to force the version of the maven dotnet plugin to 0.6 in the pom.xml file.
  2. Why do I get "Embedded error: Can not analyze the project. This measure has already been saved: ..." ?
    You are using sonar 2.1.X, you need to launch sonar with "mvn sonar:sonar -Dsonar.dynamicAnalysis=false"
  3. Why do I get MSBuild error such as "error MSB4126: The specified solution configuration "Debug|HPD" is invalid"?
    You are using a 64 bit windows OS. There is an environment variable "Platform=HPD" that makes msbuild fail. Try to run "set platform=[enter]" then "mvn sonar:sonar..."
  4. Why do I have unit tests running but no coverage measures ?
    You are using a 64 bit windows OS and partcover to gather coverage metrics. Out of the box partcover is incompatible with 64 bit systems. You need to either use the CorFlags tools on partcover and gallio as explained on the maven dotnet plugin site or use instead NCover.
  5. Why do I have coverage measures but no test measures ?
    You are using sonar dotnet 0.4 and you have executed "mvn sonar:sonar -Dsonar.dynamicAnalysis=false". Try with simply "mvn sonar:sonar".
  6. Why do I get "Failure executing commandline, Error while executing process" errors ?
    The maven plugin maven-dotnet-plugin was not able to find one of the external tool needed to perform the analysis. Check your maven settings as described on the maven-dotnet-plugin site.
  7. On Windows7 I get *The Silverlight 3/4 SDK is not installed error messages, why so much hate ?*
    64bits msbuild cannot be used with silverlight. Check that you are not using a 64bits msbuild by taking a look at properties dotnet.3.5.sdk.directory and dotnet.4.0.sdk.directory. "Framework64" should not be present in the path.
  8. The analysis fails during CPD execution, throwing a stack overflow error. What can I do ?
    As a workaround, until cpd implementation used in the dotnet plugin is more robust, you can increase the size of the java stack. This can be done using parameter "-Xss". To increase the size used by maven to 2 mb, the command looks like that : set MAVEN_OPTS=-Xss2m

If none of those works, run the build by adding "-X" to the command line and send the output to the user mailing list (user@sonar.codehaus.org)

Labels
  • None