I upgraded my sonar version from 3.7 to 4.3.2. I understand from the release notes that alerts have been replaced with quality gates concept and when I log in to the dashboard, I do not see any quality profile that I had created before. I created a quality gate and set that as the default one.
On executing sonar from maven using sonar maven plugin, I get the following error - You must install a plugin that supports the language 'java'. I use the jacoco plugin to get multi module code coverage.
Is there any change that I need to do in my POM to get it running again?
This error occurs when installed plugins (directory extensions/plugins) are not copied before upgrading. Error logs will be improved in next versions.
Related
I am unable to execute sonar analysis for PMD. I have installed a plugin for pmd (sonar-pmd-plugin-3.2.1.jar) manually and restarted the sonarqube. triggered jenkins build for the pmd analysis where it throw the error, unsupported java version for pmd. Please find snippet for reference.
Here are details for the plugins I have used:
SonarQube : 7.1
Jenkins : 2.164
PMD plugin : sonar-pmd-plugin-3.2.1.jar (manually placed under extensions folder in SonarQube)
Java Plugin: sonar-java-plugin-5.2.0.13398.jar (under extensions folder in SonarQube)
Sonar scanner: sonar-scanner-4.2.0.1873-linux
JDK : 1.8
Work around:
Have tried adding below both entries in sonar-scanner.properties file.
sonar.java.source=1.8
sonar.java.source=8
Have changed multiple plugins for PMD and JAVA under SonarQube, here are the reference of plugin versions:
I have attached the Jenkins build logs.
Note this is for the SpringSource plugin.
When I try to import a Gradle project in Eclipse I am getting the following error:
Project location doesn't exist; See error log for details.
The stacktrace error is basically this:
Caused by: java.lang.IllegalArgumentException: Project location doesn't exist
I did some research, and a Gradle defect (https://issuetracker.springsource.com/browse/STS-3158) mentions that error handling was improved with a more useful error message, including the project location.
I have Gradle 1.7 now on my machine; however Eclipse/Springsource keeps using Gradle 1.2. How do I get it to use 1.7 (or even 1.8)
I recommend to check "Preferences->Gradle->Use Gradle wrapper's default" and install the Gradle Wrapper for all builds in question. Then Eclipse will automatically pick the right Gradle version for each build (and nobody has to install Gradle manually).
Coming across "Sonar version 3.6 is required to perform local analysis" message
when try to use Sonar Local Analysis in eclipse.
I just installed latest from CodeHaus
where the Compatibility Matrix is saying it 3.6+.
I am using Eclipse: Juno 4.2, with following plugins installed:
Sonar Java Analyser 3.2.0.20130627-1142-RELEASE org.sonar.ide.eclipse.jdt.feature.feature.group SonarSource
Sonar m2e Connector 3.2.0.20130627-1142-RELEASE org.sonar.ide.eclipse.m2e.feature.feature.group SonarSource
Any ideas?
Are you running a sonarqube server?
I don't think you can use the plugin without the server running to connect to to do the analysis.
http://docs.sonarqube.org/display/SONAR/SonarQube+in+Eclipse
For the purposes you are looking at, I am assuming personal use, you could probably get away with the standalone instance of SonarQube, using the H2 embedded database.
Local Analysis Parameters
Parameters to configure local analysis can be set in various places. Here is the hierarchy of parameters:
Parameters defined in the SonarQube Web UI
Parameters set in the pom.xml file (for Maven projects only, with the
m2e connector installed) will override parameters defined in the UI
Parameters defined in Eclipse will override parameters defined in
the pom file (go to Window > Preferences > Sonar > Local analysis
properties)
Parameters defined at project level in Eclipse will override
parameters defined at Eclipse level (right click on the project and
go to Properties > Sonar > Local analysis properties)
Excluding Plugins
Some plugins (useless for a local analysis) can be skipped while performing a local analysis thanks to the sonar.dryRun.excludePlugins property (Settings > Configuration > General Settings > General).
The default value is 'devcockpit,pdfreport,report,scmactivity,views'. For example, to skip the Build Stability plugin (due to https://jira.codehaus.org/browse/SONARIDE-346), set the property to 'devcockpit,pdfreport,report,scmactivity,views,buildstability'.
Here is where I found this information: Running Sonar Qube In Eclipse
Double Check your settings
You might also want to double check your settings. The plugin will install the sonar instance for you for local analysis on localhost:9000. If you deleted this, this might be giving you the errors. You should have 2 servers listed on the config page, localhost, and your remote server
Refer back to this page too: Configuring Sonar With Eclipse
With Sonar plug-in 3.0 local analysis could be launched fine.
With Sonar plug-in 3.2 I get the same error as you.
Please choose "Install new software..." and enter URL :
http://dist.sonar-ide.codehaus.org/eclipse-archives/3.0.0/
I had the same problem because I updated the eclipse plugin but forgot to update the sonar-server (SonarQube).
After following the upgrade guide and installing SonarQube 3.6.2 it worked again.
I have installed the sonar eclipse plugin in eclipse Juno. I put the groupid and the artifactid into the proper lines, however I get an error:
Unknown exception
How to configure the sonar plugin properly in eclipse?
You need to install Sonar on a server (or run it on your machine for testing). Then you need to configure it in the Eclipse properties and choose it from the drop-down in the associate with sonar dialog (unless it runs on your machine, in which case it is already available from the drop down).
Before you can associate a project with sonar, you need to run the sonar analysis on that project (usually using maven). Take a look at the sonar documentation to get more information.
I downloaded the TestNG NetBeans Plugin and tried to install it in my NetBeans 6.8. I'm running NetBeans IDE 6.8 (Build 200912041610).
When I click install, I get this message:
Some plugins require plugin External
Execution Support to be installed. The
plugin External Execution Support is
requested in version >= 1.19 but only
1.18.1 was found. The following plugin is affected: TestNG
Support
Some plugins require plugin Common
Test Runner API to be installed. The
plugin Common Test Runner API is
requested in version >= 1.13 but only
1.12.1 was found. The following plugin is affected: TestNG
Support
Some plugins require plugin Utilities
API to be installed. The plugin Utilities API is requested in version >= 8.0 but only 7.31.2.1 was found. The following plugin is affected:
TestNG Support
Some plugins require plugin
org.openide.util.lookup to be
installed. The plugin
org.openide.util.lookup is requested
in version 8.0. The following plugin
is affected: TestNG Support
Some plugins not installed to avoid
potential installation problems.
Is it possible to use the TestNG plugin with Netbeans 6.8?
The plugin manager doesn't even seem to know about any of the dependency plugins. Is the TestNG plugin build against a beta or experimental version? I have updated all of my plugins to the latest versions.
Update
I went ahead and built the module from the Netbeans 6.8 branch. It installs fine now. Unfortunately, when I run the tests, I can see the ant output, but the TestNG view says "No tests Executed." I'll keep fiddling with it to see if I can get it working.
I took a quick look at this. It appears that the nbm file that you can download from the wiki page that you referenced is compiled against the trunk of the NB sources, not the bits that are released as NetBeans 6.8.
I have sent a note to the developer about this.
You can build the NBM yourself, but it is pretty painful, since you have to get the contrib repository.
This is embarrassing not able to use either the old version of TestNG or new version of TestNG in NetBeans. Any one kindly create a correct TestNG plugin for version 6.8.
Unfortunately, I don't think anyone has been working on the TestNG Netbeans plug-in in a while, so I'm not surprised to hear you are running into difficulties. Try posting your question on their forums?
Otherwise, I continue to work actively on the Eclipse plug-in (new version released a few weeks ago) and TestNG is supported natively by IDEA...
Hope this helps.