Skip to content

Configuration of descendant projects

Jonathan Austin edited this page Jul 2, 2019 · 3 revisions

The source of truth for the configuration of descendant projects is, of course, the pom.xml files. The following explains the properties which are externalised and any default set-up which may cause consternation.

BorderTech Parent

Properties

The following properties may be used to affect parts of the build and deployment of a descendant project.

  • maven.compiler.source: default is 1.8
  • maven.compiler.target: default is 1.8
  • project.build.sourceEncoding: default is UTF-8

Distribution Management

  • stagingBaseUrl: default https://oss.sonatype.org/: the base of staging and snapshot URLs for deployment.
  • stagingUrl: the deployment staging URL
  • snapshotUrl: the URL for snapshot releases
  • stagingId: the ID used for distribution management

QA Parent

Properties

Global property for QA tools:

  • bt.qa.skip, default true: global switch for common QA plugin skip properties (see below)

Individual properties to override QA tools:

  • checkstyle.skip, default true: property to skip checkstyle plugin
  • spotbugs.skip, default true: property to skip spotbugs plugin
  • pmd.skip, default true: property to skip pmd plugin
  • cpd.skip, default true: property to skip cpd plugin

Other plugin properties:

  • dependency-check.skip, default false: property to skip OWASP dependency checker plugin
  • enforcer.fail, default true: property to skip enforcer plugin

Dependency check broke my build :(

Check the following:

  • Behind a firewall? Have you configured a mirror or given the plugin proxy credentials?
  • Do you have vulnerabilities? Fix 'em!.
  • Don't want it at all? Then set dependency-check.skip property to true

Plugins used in QA Parent

Refer to the plugins for all override details: