anchor.diff:  
   then, configure the following build plugins:
   
  -[code,xml]
  +[source,xml]
   ----
   <plugin>
     <artifactId>maven-compiler-plugin</artifactId>
     <version>${version.plugin.compiler}</version>
     <configuration>
  -    <source>${maven.compiler.source}</source>
  -    <target>${maven.compiler.target}</target>
  -    <encoding>${project.build.sourceEncoding}</encoding>
  +    <source>1.8</source>
  +    <target>1.8</target>
  +    <encoding>UTF-8</encoding>
       <compilerArgument>-proc:none</compilerArgument>
     </configuration>
   </plugin>
  
positive.code: }
  ----
  
  or even more interestingly, you can leverage MongoDB's geosearch capabilities to find
  all `BikeStation` that are `IN_SERVICE` and within an area:
  
  [code,java]
  ----
  import org.lambdamatic.mongodb.types.geospatial.Location;
  ...
  
negative.code: }
  ----
  
  The `Location` class is a special data-type provided by Lambdamatic. It is converted
  into a custom BSON document or query document.
  
  See the https://github.com/lambdamatic/lambdamatic-mongodb-citibikesnyc[NYC Bike Stations sample application] for more details.
  
  ===== Combining Operators
  
  
  ===== Queries on Collections
  
  *TODO*
  
  ===== Queries on Maps
  
  *TODO*
  
  
  ==== Projections
  
  In some cases, users do not want to retrieve all the documents'fields from MongoDB,
  but only the ones that need to be processed in the business layer or displayed in the UI.
  Lambdamatic supports projection as well, using the following syntax:
  
  [code,java]
  ----
  