How to Use
Just add the following parent declaration in your project parent POM:
<?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.codehaus.sonar-plugins</groupId> <artifactId>parent</artifactId> <version>14</version> <relativePath>../parent</relativePath> </parent> ... </project>
Just change Change the version of the parent pom you used previously. Have a look at each the release note of notes for each version you upgrade to see if there are some any notable changes which will require you to modify something in your project.
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.
<inceptionYear>2010</inceptionYear> <organization> <name>MyCompany</name> <url>http://mycompany.com</url> </organization> <licenses> <license> <name>GNU LGPL v3</name> <url>http://www.gnu.org/licenses/lgpl.txt</url> <distribution>repo</distribution> </license> </licenses>
You can change the values of the following properties to control license headers of your source files:
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 Maven plugins to use.
This isn't recommended, but could it may be useful to use a new newer version of a plugin not yet available Maven plugin than is specified in the parent POM or to workaround a bug by using another version. In all cases don it may be necessary to use another version of a plugin in order to work around a bug. If you must do so, do 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 one than 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 " and
java.min.version". This and available plugins plugin updates can be checked with help of versions-maven-plugin.