I take pride in the cleanliness of my code. One of the major ways to ensure my code is in fact clean is to use a static code analysis tool. SonarQube (formerly known as Sonar) is definitely my go to tool for this. Below are the steps I follow to integrate with SonarQube.
In the maven pom.xml I add the sonar plugin, and properties it requires:

When starting at a new client you generally have to remember passwords on a bunch of *nix machines – dev, uat, prod and various others. I usually securely store those passwords somewhere and ideally never have to look them up again. Instead, I distribute my public key to the appropriate servers so that I am never actually prompted for a password.

When starting at a new client I often have to setup my development environment from scratch.

Another one of those tasks that I always do when starting at a new client is configuring Git just the way I like it.

I’ve been using Maven for quite some time, and always end up forgetting these very useful commands. Figured that posting them here would help us all out!