[
https://issues.apache.org/jira/browse/KAFKA-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867411#comment-17867411
]
Chris Egerton commented on KAFKA-16068:
---------------------------------------
@johndoe I've reassigned this to myself; let me know if you'd like to continue
working it, though!
> Use TestPlugins in ConnectorValidationIntegrationTest to silence plugin
> scanning errors
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-16068
> URL: https://issues.apache.org/jira/browse/KAFKA-16068
> Project: Kafka
> Issue Type: Task
> Components: connect
> Reporter: Greg Harris
> Assignee: Chris Egerton
> Priority: Minor
> Labels: newbie++
>
> The ConnectorValidationIntegrationTest creates test plugins, some with
> erroneous behavior. In particular:
>
> {noformat}
> [2023-12-29 10:28:06,548] ERROR Failed to discover Converter in classpath:
> Unable to instantiate TestConverterWithPrivateConstructor: Plugin class
> default constructor must be public
> (org.apache.kafka.connect.runtime.isolation.ReflectionScanner:138)
> [2023-12-29 10:28:06,550]
> ERROR Failed to discover Converter in classpath: Unable to instantiate
> TestConverterWithConstructorThatThrowsException: Failed to invoke plugin
> constructor (org.apache.kafka.connect.runtime.isolation.ReflectionScanner:138)
> java.lang.reflect.InvocationTargetException{noformat}
> These plugins should be eliminated from the classpath, so that the errors do
> not appear in unrelated tests. Instead, plugins with erroneous behavior
> should only be present in the TestPlugins, so that tests can opt-in to
> loading them.
> There are already plugins with private constructors and
> throwing-exceptions-constructors, so they should be able to be re-used.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
