anchor.diff:  By default, only the maven builds who reach the "deploy" phase will trigger downstream builds.
   image:docs/images/downstream-pipeline-trigger-threshold-lifecycle.png[]
   
  -[#feature-os]
  -=== Linux, Windows and MacOSX support
  -
  -The Pipeline Maven Plugin works with Linux, Windows and MacOSX build agents.
  -
  -*Maven build on a Windows agent*
  -
  -[source,syntaxhighlighter-pre]
  -----
  -node ("windows") {
  -  stage ('Build') {
  -
  -    git url: 'https://github.com/cyrille-leclerc/multi-module-maven-project'
  -
  -    withMaven(...) {
  -
  -      bat "mvn clean install"
  -
  -    } // withMaven will discover the generated Maven artifacts, JUnit Surefire & FailSafe reports and FindBugs reports
  -  }
  -}
  -----
  -
   [#feature-mvnw]
   === Support of Takari's Maven Wrapper 'mvnw'
   
  
positive.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 an utility (e.g. invocations of "maven-help-plugin:3.2.0:evaluate"...)
  | +
  |`withMaven(options: [mavenLinkerPublisher(disabled: true)],...)`
  |`skip-maven-linker-publisher`
  
negative.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 markers file must be located in the home directory of the build.
  
  ==== Implicit or Explicit activation of Publishers
  
  