I'm looking into upgrading Sonar, from 3.2.1 to 3.7.1. In our current system, we have the fb-contrib plugin installed and many of its violations enabled. However, in the latest version, I do not see it listed in Update Center -> Available Plugins. I've looked at the release notes for each release and I do not seen any mention of fb-contrib. I've looked at the plugins homepage and it isn't clear. Does anyone know if it is still supported?
Thanks.
It's not compatible with version 3.7. See http://docs.codehaus.org/display/SONAR/Plugin+version+matrix
Related
What are the difference between net.wasdev.wlp.maven.plugins and io.openliberty.tools liberty-maven-plugin and which one should I use ?
New, preferred (3.x) version
io.openliberty.tools:liberty-maven-plugin
The io.openliberty.tools one is the newer, better version of the liberty-maven-plugin, and the one you'll likely want to use for new development.
Older (2.x) version
net.wasdev.wlp.maven.plugins:liberty-maven-plugin
The older net.wasdev.wlp.maven.plugins plugin is what evolved into the newer io.openliberty.tools plugin.
Along with the move from version 2.x to version 3.x of the liberty-maven-plugin, the groupId was also changed from net.wasdev.wlp.maven.plugins (versions 1.x-2.x) to io.openliberty.tools (version 3.x and beyond).
Why use the newer plugin?
Both versions of the plugins can be used to work with (install, deploy to, etc.) either Open Liberty or WebSphere Liberty servers. (so that is not a concern in choosing one vs. the other).
The newer V3 plugin provides the helpful new "dev mode" support. Plus you'll find a lot more recent material using this version such as the Open Liberty guides.
It also enhances and streamlines some of the other goals and configuration (besides "dev mode"). There's a summary of the 3.x enhancements here.
So at this point the only reason to use the 2.x plugin from net.wasdev.wlp.maven.plugins would be to continue with a project already using this version of the plugin (unless or until you're ready to migrate).
After I replace version 4.1.2 clover-maven-plugin instead of version 3.1.3 maven-clover2-plugin, and then i got an error as below:
But i am confused with "Renewals and upgrades of Clover are no longer available effective April 11, 2017. If you require an upgrade to a different license tier we recommend switching to the open-source version. Open-source Clover does not require a license tier and offers unlimited usage."
https://www.atlassian.com/licensing/clover#-4
Can someone help have look?
Atlassian has open-sourced Clover on April 11, 2017. It means that all binaries published before this date are the commercial ones and thus they require a license key. It applies to all Clover versions up to 4.1.2. Please note that historically the Maven Clover Plugin has been renamed, so its artifactId is:
maven-clover2-plugin till version 4.0.6
clover-maven-plugin for versions 4.1.1-4.1.2
In order to use the open-source version of Clover, you have to build it from sources (Atlassian published source code only and does not host any open-source binaries at the moment).
However, as Clover-lover :-) I've prepared binaries - they're named OpenClover. It's a fork based on Atlassian Clover sources. See the website: http://openclover.org. The Maven plugin is org.openclover:clover-maven-plugin, as Haven Lin wrote.
Maven by default uses these versions of plugins such as clean, compile, jar etc. if I don't override them in my pom.xml.
Should I be using more recent version of these plugins? For example, the current version of maven-compiler-plugin is 3.6.1 while the default is 2.5.1. Or, are the default versions reasonable enough that anyone not consciously depending on newer features need worry?
The maven way is "convention over configuration", so if you're wondering about not using the default parameters when running a maven build, you should have a specific use case that is not covered by the default version.
Here for example, (according to here) the install plugin is still at version 2.5.2, so that would point to me that using 2.5.1 is not such a bad choice by default.
I think the biggest difference comparing version (I might be wrong) is the upgrading of compatible version as for example this pseudo release note of the maven compiler.
Now my sonarQube version is sonar-5.6.5 and I want to use sonar-redmine plugin.
but this plugin was deprecated in my version.
How can i use this plugin in my version?
What plugin is a substituable sonar-redmine plugin?
I want to integrate SonarQube and redmine.
The extensions points used by the SonarQube Redmine plugin are no longer supported in SonarQube 5.6 LTS. This is why this plugin is deprecated.
For your information, you won't find any replacement for this kind of plugin. If you want to better understand why this feature has been removed from SonarQube extension points, please read the "Stop planning; fix the leak!" blog post that I wrote on this topic - in which you can replace "JIRA" by "Redmine".
I'm setting up a project environment for a bigger Java project and plan to use SonarQube with PMD, Findbugs and JaCoco. Theses tools are already included in SonarQube with the Java Ecosystem Plugins, but not all the new versions are supported.
In specific, PMD has only support for version 4.3 (http://docs.codehaus.org/display/SONAR/PMD+Plugin), which is 2 years old now. Is there any possibility to install/use the newest version of PMD with SonarQube?
The answer is no.
For your information, you shouldn't need to use PMD anymore. See http://www.sonarqube.org/already-158-checkstyle-and-pmd-rules-deprecated-by-sonarqube-java-rules/.
You can also follow and vote for http://jira.codehaus.org/browse/SONARJAVA-26