anchor.diff:  [INFO] ------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] ------------------------------------------------------------------------
  -```
  +----
   
   The validation passed, and 4 endpoints was validated. Now suppose we made a typo in one of the Camel endpoint uris in the source code, such as:
   
  -    @Uri("timer:foo?period=5000")
  +[source,java]
  +----
  +@Uri("timer:foo?period=5000")
  +----
  +
   
   is changed to include a typo error in the `period` option
   
  -    @Uri("timer:foo?perid=5000")
  +[source,java]
  +----
  +@Uri("timer:foo?perid=5000")
  +----
   
   And when running the validate goal again reports the following:
   
  -```
  +----
   [INFO] ------------------------------------------------------------------------
   [INFO] Building Camel :: Example :: CDI 2.19.0
   [INFO] ------------------------------------------------------------------------
  
positive.code: For that you can use Apache Karaf or Apache ServiceMix.
  You can use the applicationContextUri configuration to specify an explicit blueprint XML file, such as:
  
      <plugin>
        <groupId>org.apache.camel</groupId>
        <artifactId>camel-maven-plugin</artifactId>
        <configuration>
          <useBlueprint>true</useBlueprint>
          <applicationContextUri>myBlueprint.xml</applicationContextUri>
          <!-- ConfigAdmin options which have been added since Camel 2.12.0 -->
          <configAdminPid>test</configAdminPid>
          <configAdminFileName>/user/test/etc/test.cfg</configAdminFileName>
        </configuration>
      </plugin>
  
  The `applicationContextUri` will currently load the file from the classpath, so in the example above the
  `myBlueprint.xml` file must be in the root of the classpath.
  
negative.code: 
  From the source of Camel you can run a CDI example via
  
  ----
  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:
  
  [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.
  
  [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.
  