I have generated my cobertura code covergage report using ant from netbeans but not able to import cobertura generated xml report into sonar.
My plugin version using is as below :
sonar-java-plugin-2.2
sonar-cobertura-plugin-1.6
Sonarqube version 4.3
Also code coberage generated junit xml report is generated with name "TEST-" followed by class name with full package due to which resource found error showing while analyzing project in sonar using sonar-runner due to which 0-test file analyzed showed while analysis but that i resolved by removing prefix "TEST" from java file.
Please Help to import sonarqube generated xml report into sonar.
The version 1.6 of cobertura plugin contains a bug that prevent import of reports. The 1.6.1 version fix the issue.
Related
When analyzing C# project with TFS 2015 vNext build, I get the following error:
The folder
'D:\Builds_Agent1_work\4\s\System\IPS\Files\Logo\MasterDesigns\Logo_11_Seal_of_Pinellas_County'
does not exist for
'DEV_ScriptAdvisorPBM_SonarQube:DEV_ScriptAdvisorPBM_SonarQube:9C5E1BB5-E446-45C8-9CE6-5F9896D0D063'
(base directory = D:\Builds_Agent1_work\4\s\System\IPS)
I think it's because there is a file called "Logo_11_Seal_of_Pinellas_County,_Florida.png" but SonarQube thinks it's "Logo_11_Seal_of_Pinellas_County".
I tried /d:sonar.exclusions=**\MasterDesigns\* to ignore the entire directory where "Logo_11_Seal_of_Pinellas_County,_Florida.png" is located but still same error.
Any suggestions to fix this issue? Thx.
SonarQube 6.5 C# plugin.
This bug is tracked by SONARMSBRU-199 which was fixed in the Scanner for MSBuild v4.1.
The bug report as mentions a workaround for excluding a single file.
FYI support for MSBuild 12 was dropped in the Scanner for MSBuild v4, so if you upgrade the version you will need to make sure you are using a compatible version of MSBuild.
I am trying to insert sonarqube setup on build.xml, getting unsupported error.
My build Java version support 1.6
Ant.sonar.qube support 2.5
If I use have version 1.8 my ant sonar command is working.ant command is not working.if I use java 1.6 ant is working and ant sonar is not working.
You already know exactly what your problem is:
If I use have version 1.8 my ant sonar command is working
...
if I use java 1.6 ant is working and ant sonar is not working.
You're facing incompatibility with the version of Java you're trying to use. Since analysis will not work with 1.6, you're best off upgrading to Java 8 and working to make whatever your other Ant target is work with that.
Generate PDF file using jasper report in Grails 3.1.8 . But when I
add dependencies some error is occurred. I can't adding any jasper report dependencies
in Grails 3.1.8. Please help me or any idea to use jasper report plugin in grails 3.1.8.I already used
(1)
compile "org.grails.plugins:jasper:1.11.0"
(2)
compile 'com.lowagie:itext:2.1.7.js2'
compile 'net.sf.jasperreports:jasperreports:6.2.1'
The plugin org.grails.plugins:jasper:1.11.0 is not grails 3 compatible. It is only up to Grails 2.x
There is a plugin for Grails 3 version here.https://grails.org/plugins.html#plugin/grails-jasper.
In other hand, you could run grails dependency-report for seeing what it is happening. It seems that there is a conflict between dependencies. But as I said, that plugin probably won't work with your project.
I was having the same issue. I fixed it by downloading the jasper report jar and kept it in a folder named lib, then showed the path in dependencies like this.
compile files('lib/jasperreports-5.5.0.jar')
We are using Visual Studio 2015 (original release, no update) with SonarQube and Jenkins, and keep getting the message:
WARN - * The use of MSBuild 12 or the sonar-runner to analyze C# projects is DEPRECATED *
However, we are using MSBuild 14, SonarLint, and the SonarQube scanner for MSBuild. This is confirmed at the beginning of the log:
SonarQube Scanner for MSBuild Begin Step 2.0
Loading analysis properties from c:\Program Files (x86)\tools\MSBuild.SonarQube.Runner-2.1\SonarQube.Analysis.xml
15:25:15.073 Updating build integration targets...
15:25:15.079 Fetching analysis configuration settings...
15:25:15.51 Generating rulesets...
15:25:16.629 Provisioning analyzer assemblies...
15:25:16.63 Installing required Roslyn analyzers...
SonarQube Server is 5.1.2
We used the instructions at http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+MSBuild#AnalyzingwithSonarQubeScannerforMSBuild-msbuildcompat and the Jenkins integration
http://docs.sonarqube.org/display/SCAN/From+Jenkins
I found the question SonarQube warning on MSBuild version but I think we are correctly using SonarLint. What is the cause of the deprecation message?
We finally solved this issue by updating everything: We updated the C# plugin in Sonarqube and all Jenkins Plugins (including the msbuild plugin). After that, the deprecation message no longer occurs.
I am trying to get files annotated with lombok.jar to compile with maven 3 using one of the Java 8 early access releases. I have maven configured to use the java 8 compiler. The code that I am compiling has a dependency defined for lombok 0.12 in maven central. However when I compile with maven I get the following error:
[ERROR] symbol: variable log
[ERROR] location: class Foo
[ERROR] C:.....\Foo.java:[319,33] error: cannot find symbol
I have run maven in debug mode and the classpath entry specified states that the lombok 0.12 jar file is in the classpath of the project. Additionally, I tried setting lombok.jar specifically in my classpath (and I can see in env.CLASSPATH in maven debug mode) which creates the same results.
Everything builds and compiles just fine in eclipse -- what am I doing wrong with the maven configuration/environment such that I can't get compilation to success outside of eclipse?
To answer my own question -- the issue is with the version of lombok (0.12.0) not working well with java 8. To fix, I used the cutting edge version of lombok , installed it into my local maven repo with the line
mvn install:install-file -Dfile=lombok-edge.jar -DgroupId=org.projectlombok -DartifactId=lombok-edge -Dversion=0.12.1 -Dpackaging=jar
and then changed the dependencies in my pom accordingly.
Once I did that, I was able to compile from command line maven.