Currently, the BV API signature check is configured in a separate profile in the engine pom.xml. It'd seem more consistent to move this to tck-runner module instead, as the signature check really is a part of the TCK.
More importantly, the compatibility check should also be set to “strictcheck”, to prevent _any_ changes in the validated API. Currently, e.g. an added annotation or method in the new BV API version would not be discovered. This can be achieved like so:
{code:xml}<configuration>
<action>strictcheck</action>
<packages>javax.validation,javax.validation.bootstrap,javax.validation.constraints,
javax.validation.constraintvalidation,javax.validation.executable,javax.validation.groups,
javax.validation.metadata,javax.validation.spi,javax.validation.valueextraction
</packages>
<sigfile>${project.build.directory}/api-signature/validation-api-java8.sig</sigfile>
</configuration>{code}
|
|
