We're updating the issue view to help you get more done. 

Move TCK signature check to tck-runner module

Description

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:

 

1 2 3 4 5 6 7 8 <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>

 

Environment

None

Status

Assignee

Unassigned

Reporter

Gunnar Morling

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Priority

Major