You should see the venerable 'Hello, World!' message formatted as a JSON object: Verify that everything is working by right-clicking the Application.java file in IntelliJ and click 'Run.'Īfter running it, test that everything is working OK by navigating to in your browser. Once you have everything imported, your project window should look something like the following: Either way, go ahead and take a few minutes to get the project running using your preferred build environment and import it into IntelliJ. If you have an existing project that you'd like to use instead, by all means use that. We'll also take the SonarLint IntelliJ plugin for a spin, so be sure to download the community edition of IntelliJ. For this guide, we'll use the restful Java web service from the Building a RESTful Web Service Spring guide project, and we'll use Gradle as a build tool. Create a Simple Projectīefore diving into using SonarLint and SonarQube, we need a project to work with. Simple and straightforward code makes everything easier. Thus, it reduces the cost of ongoing development as well as the cost associated with maintenance.

Using tools like these will help preserve the quality of the code being developed. This article takes a look at integrating with the SonarLint IntelliJ plugin for analyzing code while it's being worked on, as well as integrating with SonarQube through the SonarCloud offering for analyzing and tracking quality issues across all of your organization's projects. It's been a major player in the open-source and commercial space, and it's been around for quite a while. Among the leading tools out there is SonarQube from SonarSource. While modern compilers do a really good job of catching some of the errors that linting tools will find, these tools have evolved to keep up with the times. Jones back in 1978 while porting Unix to a 32-bit machine. Analyzing source code for syntax or quality issues is often referred to as linting, coined by the computer scientist Stephen C. Ensuring that a codebase is following certain quality guidelines isn't a new topic. Code is often copied and pasted across modules, or you have that one developer who keeps 'forgetting' to follow the agreed-upon syntax when it comes to naming member variables we all discussed in that one meeting years ago. As the number of lines in our code grows, the quality of the code being written usually suffers. Over the years, software has grown in size and complexity.

Phpstorm blog