|Table of content|
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 overrided by projects to customize the default behavior of maven defined in the parent pom.
Define licenses, inceptionYear and organization :
You can change values of 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 using following command :
Maven plugins versions
The parent pom defines in a set of properties all recommended versions of maven plugins to use.
This isn't recommended but could be useful to use a new version of a plugin not yet available in the parent POM or to workaround a bug by using another version. In all cases don not forget to report to us the change you need. If it's good for one project, it could be useful for others.
Each project/module can override a version of a plugin to use a different from the one defined in parent. For example to change 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 not possible if you are behind proxy - see SONARPLUGINS-1457
All plugins specified in POM, must be compatible with "maven.min.version" and "java.min.version". This and available plugins updates can be checked with help of versions-maven-plugin.