anchor.diff:  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:
   
  -      <plugin>
  -        <groupId>org.apache.camel</groupId>
  -        <artifactId>camel-maven-plugin</artifactId>
  -        <version>2.19.0</version>
  -        <executions>
  -          <execution>
  -            <configuration>
  -              <includeTest>true</includeTest>
  -            </configuration>
  -            <phase>process-test-classes</phase>
  -            <goals>
  -              <goal>validate</goal>
  -            </goals>
  -          </execution>
  -        </executions>
  -      </plugin>
  -
  +[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
   
  
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: 
  You would need to configure the camel:run plugin to use blueprint, by setting useBlueprint to true as shown below
  
  [source,xml]
  ----
  <plugin>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-maven-plugin</artifactId>
    <configuration>
      <useBlueprint>true</useBlueprint>
    </configuration>
  </plugin>
  ----
  
  This allows you to boot up any Blueprint services you wish - whether they are Camel-related, or any other Blueprint.
  
  