How to Use
Just add the following parent declaration in your project parent POM:
How to Upgrade
Just change the version of the parent pom you used previously. Have a look at each release note of each version you upgrade to see if there are some notable changes which require to modify something in your project.
How to Configure
The parent defines and uses a set of custom properties that can be reused and/or overridden by projects to customize the default behavior of Maven defined in the parent pom.
Define licenses, inceptionYear and organization:
You can change the values of the following properties to control license headers of your source files:
Possible values are : "GNU LGPL 3", "AL2", "MIT".
GNU LGPL 3
Now you can add/update headers of your source files with the following command:
Maven plugins versions
The parent pom defines a set of properties recommended for all versions of Maven plugins.
Each project/module can override a version of a plugin to use a different from the one defined in parent. For example to change the version of sonar-packaging-maven-plugin you can use following code snippet:
|Release profile||release||Deactivated by default. Activated during release. Can be activated with -Prelease||Generates javadoc artifacts.|
|Integration tests||integration-tests||Deactivated by default. Can be activated with -Pintegration-tests||Launch integration tests from JUnit using the failsafe plugin.|
Deployment is not possible if you are behind proxy - see SONARPLUGINS-1457
All plugins specified in the POM, must be compatible with
java.min.version. This and available plugin updates can be checked with help of versions-maven-plugin.