anchor.diff:  }
   ----
   
  -The output message will show from which plugin the XercesParser is
  -loaded. Sample with a plugin "my_plugin" that would load an outdated
  -2.6.2 version of Xerces:
  +The output message will show from which plugin the XercesParser is loaded. Sample with a plugin "my_plugin" that would load an outdated 2.6.2 version of Xerces:
   
    class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/my_plugin/WEB-INF/lib/xercesImpl-2.6.2.jar
   
  -== How to use Maven build data in generated emails
  -
  -It is possible to use informations generated by Maven pipelines in
  -emails generated by the https://github.com/jenkinsci/email-ext-plugin.git[Jenkins Email Ext
  -Plugin].
  +== How to use Maven build data in generated emails?
  +
  +It is possible to use information generated by Maven pipelines in emails generated by the https://plugins.jenkins.io/email-ext/[Jenkins Email Ext Plugin].
   
   See https://groups.google.com/forum/#!topic/jenkinsci-users/sPAYLh1W1cM
   
  -*Sample Pipeline code to expose artifact details in emails*
  -
  -[source,syntaxhighlighter-pre]
  +.Sample Pipeline code to expose artifact details in emails
  +[source,groovy]
   ----
   env.DEPLOYEDARTIFACTS = getDeployedArtifacts()
   
  
positive.code: 
  **Using Takari's Maven Wrapper mvnw**
  
  [source,syntaxhighlighter-pre]
  ----
  node("linux-agent-running-docker") { // Linux agent with the Docker daemon
      docker.image('openjdk:8-jdk').inside { // Docker image with Java installed
          withMaven(...) {
              git "https://github.com/cyrille-leclerc/my-jar.git"
              sh "./mvnw clean deploy" // 'mvnw' command (e.g. "./mvnw deploy")
          }
  
negative.code: }
  ----
  
  === Using `withMaven` with `docker.image(...).inside{...}` to a Jenkins Declarative Pipeline
  
  NOTE: TODO: provide a sample with Jenkins Declarative Pipeline
  
  === Sample message displayed in the build logs when using withMaven in a Docker Pipeline execution environment
  
  The warning message displayed in the logs when invoking `withMaven` within Docker Pipeline:
  
  ----
   [withMaven] WARNING: "withMaven(){...}" step running within "docker.image('image').inside {...}". Since the Docker Pipeline Plugin version 1.14, you MUST:
   [withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").
   [withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")
   [withMaven] See Pipeline Maven Plugin FAQ.
  ----
  
  == How to disable the Maven Event Spy injected by the Pipeline Maven Plugin in Maven builds?
  
  It may be convenient to temporarily disable the Maven Event Spy of the Jenkins Pipeline Maven plugin, for example for troubleshooting purpose.
  
  You can disable the Maven Event Spy of the Jenkins Pipeline Maven plugin (making it no-op) doing one of the following:
  
  * Setting the environment variable `JENKINS_MAVEN_AGENT_DISABLED` to `true` in the job execution
  [source,groovy]
  ----
  withMaven() {
     sh """
  export JENKINS_MAVEN_AGENT_DISABLED=true
  