anchor.diff:  
   To benefit from dynamic value resolution you only must add the corresponding dependency to your module:
   
  -[source, xml]
  +[source, xml, subs="verbatim,attributes"]
   -----------------------------------------------
   <dependency>
     <groupId>org.apache.tamaya.ext</groupId>
     <artifactId>tamaya-resolver</artifactId>
  -  <version>{tamayaVersion}</version>
  +  <version>{tamaya_version_current}</version>
   </dependency>
   -----------------------------------------------
   
  
positive.code: blabla ${decrypt:myname} foo blabla ${decrypt:myname}
  -----------------------------------------------
  
  Hereby evaluation is repeasted until no further change of values could be detetced. In case of a endless loop
  the evaluation is broken after a (configurable) number of cycles.
  
  
  
negative.code: Currently the module defined the following resolvers:
  
  .Available Resolvers
  [cols="<.1,<.2,<.1"]
  |=======
  | _Expression_
  | _Description_
  | _Example_
  
  | +conf:<configKey>+
  | Reads another configKey and replaces the expression with the value found.
  | conf-ref=${conf:anotherConf.entryKey}
  
  | +resource:<resourceRef>+
  | Reads a resource from the current classpath and replaces the expression with the given text content.
  | cp-ref=${resource:Testresource.txt}
  
  | +file:<fileRef>+
  | Reads a resource from the current classpath and replaces the expression with the given text content.
  | file-ref=${file:c:\myFile.txt}
  
  |+url:<url>+
  |Reads an URL and replaces the expression with the given text content.
  | url-ref=${url:http://www.google.com}
  
  |=======
  
  === SPI: Implementing your own Resolvers
  