Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Table of content

How to use

Just add the following parent declaration in your project parent POM :

pom.xml

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 cutom properties that can be reused and/or overrided by projects to customize the default behavior of maven defined in the parent pom.

License

Define licenses, inceptionYear and organization :

pom.xml

TBA

Property

Description

Default value

license.name

Possible values are : "GNU LGPL 3", "AL 2", "MIT".

GNU LGPL 3

license.title

 

${project.name}

license.year

 

${project.inceptionYear}

license.owner

 

${project.organization.name}

license.mailto

 

dev@sonar.codehaus.org

Maven plugins versions

The parent pom defines in a set of properties all recommended versions of maven plugins to use.

Icon

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.

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:

pom.xml

Java version

Icon

This isn't recommended but could be useful.

To work Sonar requires Java 1.5 or later. So, your plugin should work under Java 1.5. However if you really want to have Java 1.6 as target platform, then you can use following configuration :

pom.xml

Profiles

TBA

Changelog

Loading

Version 7 (not released) (9 issues)

  • No labels