anchor.diff:  | `outputDir`     | `File`          | Output directory for generated code. 
   Default: `${project.build.directory}/generated-sources/ramler`
   
  -|===
  -
  +| `discriminatorMutable` | `boolean` | Should discriminator properties be mutable?
  +Default: `false`
  +
  +| `interfaceNameSuffix` | `String` | Suffix for interface names. 
  +This suffix is appended to the code name of a resource. The code
  +name is either specified explicitly by the `(codeName)` annotation, or implicitly by
  +the resource name, converted to camel case.
  +Default: `Resource`
  +
  +| `jacksonPropertyName` | `boolean` |  Should Java classes include `JsonProperty` annotations 
  +for properties with illegal Java names?
  +Default: `false`
  +
  +| `jacksonTypeInfo` | `boolean` |  Should Java classes include `JsonTypeInfo` annotations for type hierarchies?
  +Default: `false`
  +
  +|===
   
   
   == java-test Goal  
  
positive.code: 
  | `outputDir`     | `File`          | Output directory for generated code. 
  Default: `${project.build.directory}/generated-test-sources/ramler`
  |===
  
  
  
negative.code: 
  Ramler does not currently support header or matrix parameters.
  
  == Multiple Media Types
  
  For a resource method with a response body that supports multiple media types, Ramler will generate a separate Java method 
  for each media type and add a `@Produces` annotation to each method not matching the media type defined at class level.
  
  It is recommended to specify the generated method name with a `codeName` annotation to the alternative media type. By default,
  Ramler will simply add a numerical suffix to the RAML method name.
  
  Example:
  
    /anything:
      get:
        responses:
          200:
            body:
              application/json:
                type: object
              text/csv:
                (r.codeName): getCsv
                type: string
  
  [source,java]
  ----
  
  @Path("/anything")
  @Produces(MediaType.APPLICATION_JSON)
  @Consumes(MediaType.APPLICATION_JSON)
  public interface AnythingResource {
  
      @GET
      Map<String, Object> get();
  
      @GET
      @Produces("text/csv")
      String getCsv();
  
  }
  ----
  
  = HTML Generator
  
  The HTML generator generates a static website with three columns for types and resources, details and examples.
  
  You can customize the layout by overriding the included web resources or even by adapting the 
  http://www.trimou.org[Trimou] templates used to generate output from the parsed API model.
  
  To do so, set the configuration properties `webResourceDir` or `templateDir`, respectively.
  
  = Maven Plugin
  
  == html Goal
  
  |===
  | Parameter     | Type          | Meaning
  
  | `model`         | `String`        | RAML specification file
  
  | `outputDir`     | `File`          | Output directory for generated code. 
  Default: `${project.build.directory}/generated-sources/ramler`
  
  | `webResourceDir` | `File` | Directory with web resources to be used instead of the built-in resources.
  
  | `templateDir` | `File` | Directory with Trimou templates which take precedence over the built-in templates.
  The entry template is named `api.trimou.html`.
  
  |===
  
  
  == java Goal
  
  