We recently installed SCMActivity plugin in our 3.6.1 installation and it worked without a hitch. Now that we are prepping to move to 4.4, installing the same plugin (version 1.8) does not yield same results - svn blame is not working. I am not sure why.
Our setup is all Centos, SVN 1.8, Sonar 4.4, SCMActivity plugin 1.8.
Since SonarQube 4.5, you need to turn on SCM decoration on the Component Viewer to be able to see SCM information. See the documentation on the SCM Tab.
Related
I am trying to use maven in our project and am new to it.
checking this https://maven.apache.org/download.cgi
3.6.0 version is latest version to download.
Someone was saying there is maven 4 is latest. Not sure where to download this from and can we use this for java 8.
Which one is latest version to use?
From https://maven.apache.org/download.cgi
Apache Maven 3.6.0 is the latest release and recommended version for
all users.
Works nicely with Java 8. Note that your IDE may bundle an older version in the unlikely case you run into problems.
I am using Hudson 3.1.0 version and sonar 3.7.4 version. SInce yesterday I am getting this weird error while doing sonar analysis:
This was working fine until yesterday. sonar-maven-plugin-3.3.0.603 version is used.Can somebody help here?
You are using a version of the SonaQube Scanner for Maven that is too recent (3.3.0.603). You should lock this version (in your POM) to an older version to make sure this keeps on working correctly.
As a side note, please consider upgrading to more recent software:
SonarQube 3.7.4 is 4 years old and no more supported (which means nobody will help you in case of trouble)
Hudson is kind-of dead - the best option for you is to move on Jenkins
I tried to install sonar qube plugin from http://downloads.sonarsource.com/eclipse/eclipse/ in Mule Studio Version (3.5.0) with Mule runtime (3.4.0). For my requirement I cannot got with the latest version of studio.
The following is the error message I am getting when trying to install the plugin in Mule studio
The operation cannot be completed. See the details.
Details:
Cannot complete the install because one or more required items could not be found.
Software being installed: SonarQube Integration for Eclipse 3.5.0.20150804-1512-RELEASE (org.sonar.ide.eclipse.feature.feature.group 3.5.0.20150804-1512-RELEASE)
I tried installing the Sonar Qube plugin from the Eclipse marketplace, SonarQube 3.5.0 was listed there, but it was also mentioned that it has been deprecated and SonarLint 1.1.0 should be used instead.
I went ahead with the installation but as you reported it couldn't be completed as there seems to be a problem with the SonarQube Integration for Eclipse component.
However, can you try creating an offline copy of the update site and then try installing the plugin in studio?
http://mcuoneclipse.com/2014/07/03/replicating-an-eclipse-update-site-for-offline-usage/
EDIT
I continued with the same SonarQube installation, it took a lot of time and eclipse had to look for various alternate solutions (15 in total), but it finally came up with this dialog.
So, while installing the plugin, unselect the 2 components (if you don't need it) and move ahead with installation, I was able to successfully complete it, eclipse restarted and it was all done.
-Shanky G.
I have Bamboo version 5.2 configured on my local system.
I want to install a sonarqube plugin in my bamboo instance. I found a plugin for version 5.1, but was unable to find a plugin for version 5.2.
From where do I get the appropriate plugin and how to configure the sonar runner task with it?
it is not supported for your version of Bamboo. Its a open source plugin so you can pick it up, work on it and make it compatible with your Bamboo verison
I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!
This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.