anchor.diff:  |=========================================
   
   For example to accept any incoming data type and output Java as `com.foo.MyCustomer` you would
  -configure the the `camel-connector.json` file:
  +configure the `camel-connector.json` file:
   
       "inputDataType": "any",
       "outputDataType": "java:com.foo.MyCustomer",
  
positive.code: 
  ### Spring Boot compliant
  
  A Camel connector works great with Spring Boot. If a connector has been configured to allow configuration on the component and/por endpoint level which is done in the `camel-connector.json` file, such as
  
        "componentOptions" : [ "consumerKey", "consumerSecret", "accessToken", "accessTokenSecret" ],
        "endpointOptions" : [ "keywords" ],
  
  Then the `camel-connector-maven-plugin` will be able to generate Spring Boot auto configuration for these options.
  This allows users to essily configure these options if using Spring Boot with the connector.
  
  NOTE: There's no disctinction between component/endpoint options on spring-boot auto configuration side so all the options are flattered to a single namespace thus they appear as connector options and then the conenctor figures out where they should be applied.
  
  TIP: The options configured through spring-boot auto configuration classes can be overridden by standard endpoint options.
  
  
negative.code:     camel.connector.twitter-search.configurations.tw-search2.keywords = apache-karaf
  ------------
  
  This would create two instances of the twitter-search connector each one configured with its own list of options.
  You can now use the new connectors as standard components like:
  
  [source,java]
  ------------
  