anchor.diff:  getter methods (optionally, see below)
   * only such annotation types are annotated with constraint annotations which are constraint
   annotations themselves
  -* definition of dynamic default group sequence with @GroupSequenceProvider is valid
  +* definition of dynamic default group sequence with `@GroupSequenceProvider` is valid
   * annotation parameter values are meaningful and valid
   * method parameter constraints in inheritance hierarchies respect the inheritance rules
   * method return value constraints in inheritance hierarchies respect the inheritance rules
  
positive.code: 
  ===== Maven
  
  There are several options for integrating the annotation processor with
  http://maven.apache.org/[Apache Maven]. Generally it is sufficient to add the Hibernate
  Validator Annotation Processor as dependency to your project:
  
  .Adding the HV Annotation Processor as dependency
  ====
  [source, XML]
  [subs="verbatim,attributes"]
  ----
  ...
  <dependency>
      <groupId>org.hibernate</groupId>
      <artifactId>hibernate-validator-annotation-processor</artifactId>
      <version>{hvVersion}</version>
  </dependency>
  ...
  ----
  ====
  
  The processor will then be executed automatically by the compiler. This basically works, but comes
  with the disadavantage that in some cases messages from the annotation processor are not displayed
  (see http://jira.codehaus.org/browse/MCOMPILER-66[MCOMPILER-66]).
  
  Another option is using the http://code.google.com/p/maven-annotation-plugin[Maven Annotation Plugin].
  To work with this plugin, disable the standard annotation processing performed
  by the compiler plugin and configure the annotation plugin by specifying an execution and adding the
  Hibernate Validator Annotation Processor as plugin dependency (that way the processor is not visible
  on the project's actual classpath):
  
  .Configuring the Maven Annotation Plugin
  ====
  [source, XML]
  [subs="verbatim,attributes"]
  ----
  ...
  <plugin>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
          <source>1.8</source>
          <target>1.8</target>
          <compilerArgument>-proc:none</compilerArgument>
      </configuration>
  </plugin>
  <plugin>
      <groupId>org.bsc.maven</groupId>
      <artifactId>maven-processor-plugin</artifactId>
      <version>3.1.0</version>
      <executions>
          <execution>
              <id>process</id>
              <goals>
                  <goal>process</goal>
              </goals>
              <phase>process-sources</phase>
          </execution>
      </executions>
      <dependencies>
          <dependency>
              <groupId>org.hibernate</groupId>
              <artifactId>hibernate-validator-annotation-processor</artifactId>
              <version>{hvVersion}</version>
          </dependency>
      </dependencies>
  </plugin>
  ...
  ----
  ====
  
  
negative.code: * When using the processor within Eclipse, the check of dynamic default group sequence definitions
  doesn't work. After further investigation, it seems to be an issue with the Eclipse JSR 269 API
  implementation.
  