Maven per-project settings

As seen on SKDMan Install and SDKMan Advance Config, often a project has specific requirements.

As a developer, if I wrote more than two times the same command, I try to find a way to automate that process.

Talking about Maven, in a development environment, where we always have to pass the same parameters. In this case the “Maven common configs” file comes to help.

Create .mvn folder and maven.config file

In your root project directory create another directory named “.mvn” .

SDKMan Advance config

As you can see in previous post (“SDKMan Install”), SDKMan is an useful tool for manage your dev machine environments.

Advance config tips

An option that I recently discovered is the way to configure and install projects dependencies in one step.

For example in our .sdkmanrc file, we have the following settings:

java=11.0.11-hs-adpt

Suppose that, after some days we need to specify the Maven version (ex 3.3.9), we can add it in our file:

SDKMan - Why use it

All devs, that work on several projects, have technical requirements for each of them.

Often in a Java project, the base requirements are:

• JDK
• Maven
• Gradle
• Apache JMeter
• other strange things… :) (Hey the Demogorgon!)

In this situation, I think that the best choice is not to mess your dev system.

Before using SDKMan, I needed to edit my “JAVA_HOME”, “M2_HOME” envs variables, for each project.