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 46 Next »

Table of Contents

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

License

Define licenses, inceptionYear and organization:

pom.xml

You can change the values of the following properties to control license headers of your source files:

Property

Description

Default value

license.name

Possible values are : "GNU LGPL 3", "AL2", "MIT".

GNU LGPL 3

license.title

 

${project.name}

license.year

 

${project.inceptionYear}

license.owner

 

${project.organization.name}

license.mailto

 

dev@sonar.codehaus.org

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.

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. 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:

pom.xml

Profiles

NameIdentifierActivationDescription
Release profilereleaseDeactivated by default. Activated during release. Can be activated with -PreleaseGenerates javadoc artifacts.
Integration testsintegration-testsDeactivated by default. Can be activated with -Pintegration-testsLaunch integration tests from JUnit using the failsafe plugin.

Known Issues

Deployment is not possible if you are behind proxy - see SONARPLUGINS-1457

Development

All plugins specified in the POM, must be compatible with maven.min.version and java.min.version. This and available plugin updates can be checked with help of versions-maven-plugin.

  • No labels