anchor.diff:    </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.
  +
  +Notice its only changes of Camel routes, eg `<routes>`, or `<route>` which is supported.
  +You cannot change Spring or OSGi Blueprint `<bean>` elements.
   
   
   == camel:prepare-fatjar
  
positive.code: 
  From the source of Camel you can run a CDI example via
  
  [source,bash]
  ----
  cd examples/camel-example-cdi
  mvn compile camel:run
  
negative.code: The `camel:run` goal of the Camel Maven Plugin is used to run your Camel Spring configurations in a forked JVM from Maven.
  A good example application to get you started is the Spring Example.
  
  ----
  cd examples/camel-example-spring
  mvn camel:run
  ----
  
  