anchor.diff:  [INFO] ------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] ------------------------------------------------------------------------
  -```
  +----
   
   
   === Options
   
   The maven plugin supports the following options which can be configured from the command line (use `-D` syntax), or defined in the `pom.xml` file in the `<configuration>` tag.
   
  -|========================================
  +|===
   | Parameter | Default Value | Description
   | downloadVersion | true | Whether to allow downloading Camel catalog version from the internet. This is needed if the project uses a different Camel version than this plugin is using by default.
   | failOnError | false | Whether to fail if invalid Camel endpoints was found. By default the plugin logs the errors at WARN level.
  
positive.code: Doing so requires to specify the plugin using its fully qualified name. For example to run the goal on
  the `camel-example-cdi` from Apache Camel you can run
  
      $cd camel-example-cdi
      $mvn org.apache.camel:camel-maven-plugin:2.19.0:validate
  
  which then runs and outputs the following:
  
  ```
  [INFO] ------------------------------------------------------------------------
  [INFO] Building Camel :: Example :: CDI 2.19.0
  [INFO] ------------------------------------------------------------------------
  
negative.code: 
  Then you can run the validate goal from the command line or from within your Java editor such as IDEA or Eclipse.
  
  ----
  mvn camel:validate
  ----
  
  You can also enable the plugin to automatic run as part of the build to catch these errors.
  
  [source,xml]
  ----
  <plugin>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-maven-plugin</artifactId>
    <executions>
      <execution>
        <phase>process-classes</phase>
        <goals>
          <goal>validate</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
  ----
  
  The phase determines when the plugin runs. In the sample above the phase is `process-classes` which runs after
  the compilation of the main source code.
  