The first thing is to download the SonarLint plugin from the IntelliJ plugin manager. Particularly here we will show you the use of the SonarLint plugin for IntelliJ, but it’s equivalent for other development environments such as Eclipse or Visual Studio. This other method will allow you to execute the analysis directly from the IDE of your preference. In this way, you’ll obtain your SonarQube-generated report: As a result, you will see something like this: See the documentation about the parameters here. Mvn sonar:sonar = The name of the project in SonarQube and the version is taken from the Maven project (at the beginning of the pom file). Then, all that remains is to go to the directory of your project and execute the Maven goal with the following command: (This is for Maven 2, for Maven 3 check here ).Īt this point you have everything necessary to perform your code analysis from Maven, so it will perform the analysis in the SonarQube server that you have already installed in a Docker container (explained here ). To begin with this process, the first thing you must do is add the SonarQube plugin to your Maven project as follows: In this third and final post, we will see two SonarQube alternatives: Maven and an IDE.

In part two of this blog series on code analysis, I showed you how to do a proof of concept quickly using a SonarQube Docker image, and run the analysis from SonarQube Scanner. How to run a code analysis from Maven or an IDE

Download phpstorm sonarqube