Create a validation rule for good usage of Schema and Record

Implementation:

• create : SchemaValidator, RecordValidator,
  • implements Validator, implementing method: validate(final AnnotationFinder finder, final List<Class<?>> components)
  • but all methods in Record have no annotations.

• Add configuration parameter: talend.validation.record; talend.validation.schema
  • in org.talend.sdk.component.tools.ComponentValidator.Configuration, add : validateRecord, validateSchema
  • in org.talend.sdk.component.maven.ValidateComponentMojo, add : validateRecord, validateSchema
  • (https://talend.github.io/component-runtime/main/latest/build-tools-maven.html)

This rule will enforce usage of builders ant not eventual internal / technical methods.

The test:

• gets all TCK Java methods that return a Record.Builder or Entry.Builder
• filters only the methods that are called in package processing-functions
  makes sure that either:
• the TCK method itself is safe (preserves props from a previous builder/entry/Record)
• the TDP caller of the TCK method is safe (ex: creates a new Entry => no props to preserve)