anchor.diff:  
   From the source of Camel you can run a CDI example via
   
  -    cd examples/camel-example-cdi
  -    mvn compile camel:run
  +----
  +cd examples/camel-example-cdi
  +mvn compile camel:run
  +----
   
   === Logging the classpath
   
   You can configure whether the classpath should be logged when `camel:run` executes.
   You can enable this in the configuration using:
   
  -    <plugin>
  -      <groupId>org.apache.camel</groupId>
  -      <artifactId>camel-maven-plugin</artifactId>
  -      <configuration>
  -        <logClasspath>true</logClasspath>
  -      </configuration>
  -    </plugin>
  +[source,xml]
  +----
  +<plugin>
  +  <groupId>org.apache.camel</groupId>
  +  <artifactId>camel-maven-plugin</artifactId>
  +  <configuration>
  +    <logClasspath>true</logClasspath>
  +  </configuration>
  +</plugin>
  +----
   
   === Using live reload of XML files
   
   You can configure the plugin to scan for XML file changes and trigger a reload of the Camel routes which are contained in those XML files.
   
  -    <plugin>
  -      <groupId>org.apache.camel</groupId>
  -      <artifactId>camel-maven-plugin</artifactId>
  -      <configuration>
  -        <fileWatcherDirectory>src/main/resources/META-INF/spring</fileWatcherDirectory>
  -      </configuration>
  -    </plugin>
  +[source,xml]
  +----
  +<plugin>
  +  <groupId>org.apache.camel</groupId>
  +  <artifactId>camel-maven-plugin</artifactId>
  +  <configuration>
  +    <fileWatcherDirectory>src/main/resources/META-INF/spring</fileWatcherDirectory>
  +  </configuration>
  +</plugin>
  +----
   
   Then the plugin watches this directory. This allows you to edit the source code from your editor and save the file, and have
       the running Camel application pickup those changes.
  
positive.code: | ignoreLenientProperties | true | Whether to ignore components that uses lenient properties. When this is true, then the uri validation is stricter but would fail on properties that are not part of the component but in the uri because of using lenient properties. For example using the HTTP components to provide query parameters in the endpoint uri.
  | duplicateRouteId | true | *Camel 2.20* Whether to validate for duplicate route ids. Route ids should be unique and if there are duplicates then Camel will fail to startup.
  | showAll | false | Whether to show all endpoints and simple expressions (both invalid and valid).
  |========================================
  
  
  === Validating include test
  
negative.code: The maven plugin can also be configured to validate the test source code , which means that the phase should be
  changed accordingly to `process-test-classes` as shown below:
  
  [source,xml]
  ----
  <plugin>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-maven-plugin</artifactId>
    <executions>
      <execution>
        <configuration>
          <includeTest>true</includeTest>
        </configuration>
        <phase>process-test-classes</phase>
        <goals>
          <goal>validate</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
  ----
  
  === Running the goal on any Maven project
  
  