anchor.diff:  
   The Jenkins Pipeline Maven Plugin relies on a database to store its data (list of dependencies and of generated artifacts of each build...).
   
  -By default, the Jenkins Pipeline Maven Plugin uses an H2 embedded database but it is recommended to use an external PostgreSQL or MySQL / MariaDB database.
  +By default, the Jenkins Pipeline Maven Plugin uses an H2 embedded database, but it is recommended to use an external PostgreSQL or MySQL / MariaDB database.
   
   Configuration steps to use a PostgreSQL:
   
   * Create an empty PostgreSQL database with a dedicated PostgreSQL user with permissions for Data Manipulation Language actions (DML) and Data Definition Language (DDL) actions
   ** Tested with PostgreSQL 10.6 and 11.3
   * Install the Jenkins the https://github.com/jenkinsci/postgresql-api-plugin[PostgreSQL API] plugin
  -** Navigate to "Manage Jenkins / Manage Plugins / Available", select the "PostgreSQL API" plugin and click on "Download now and install after restart"
  +** Navigate to "Manage Jenkins / Manage Plugins / Available", select the "PostgreSQL API" plugin and click on "Download now and install after restart".
   *  Configure the Pipeline Maven Plugin to use the created PostgreSQL database
   ** Create Jenkins credentials for the PostgreSQL connection navigating to "Credentials" on the left menu
   ** Navigate to "Manage Jenkins / Global Tools Configuration" and go to the "Pipeline Maven Configuration"
  
positive.code: (2) Download https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/2.3.0-beta-1/pipeline-maven-2.3.0-beta-1.hpi[pipeline-maven-2.3.0-beta-1.hpi]
  
  (3) Marker file to temporarily disable the feature for a specific Maven build.
  Typically used to disable a reporter for a specific build that would generate too much data for the default configuration of the reporter (e.g. too many generated artifacts...) or to workaround a bug in the "`withMaven`" waiting for a fix.
  These marker file must be located in the home directory of the build.
  
  ==== Implicit or Explicit activation of Publishers
  
  
negative.code: |Maven Linker Publisher
  |Publish the Maven report on the pipeline build GUI (list of dependencies, produced artifacts, downstream & upstream pipelines). +
  This publisher should be renamed "Maven Build Report Publisher". +
  A reason to disable this publisher is typically to not "pollute" the build screen with Maven invocations when Maven is used as a utility (e.g. invocations of "maven-help-plugin:3.2.0:evaluate"...)
  | +
  |`withMaven(options: [mavenLinkerPublisher(disabled: true)],...)`
  |`skip-maven-linker-publisher`
  