The parent defines and uses a set of custom properties that can be reused and/or overrided overridden by projects to customize the default behavior of maven Maven defined in the parent pom.
Now you can add/update headers of your source files using with the following command :
Maven plugins versions
The parent pom defines in a set of properties recommended for 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 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 "maven.min.version" and "java.min.version". This and available plugins plugin updates can be checked with help of versions-maven-plugin.