[
https://issues.apache.org/jira/browse/KAFKA-8752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Dupriez resolved KAFKA-8752.
--------------------------------------
Resolution: Not A Problem
> Ensure plugin classes are instantiable when discovering plugins
> ---------------------------------------------------------------
>
> Key: KAFKA-8752
> URL: https://issues.apache.org/jira/browse/KAFKA-8752
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Alexandre Dupriez
> Assignee: Alexandre Dupriez
> Priority: Minor
> Attachments: stacktrace.log
>
>
> While running integration tests from the IntelliJ IDE, it appears plugins
> fail to load in {{DelegatingClassLoader.scanUrlsAndAddPlugins}}. The reason
> was, in this case, that the class
> {{org.apache.kafka.connect.connector.ConnectorReconfigurationTest$TestConnector}}
> could not be instantiated - which it does not intend to be.
> The problem does not appear when running integration tests with Gradle as the
> runtime closure is different from IntelliJ - which includes test sources from
> module dependencies on the classpath.
> While debugging this minor inconvenience, I could see that
> {{DelegatingClassLoader}} performs a sanity check on the plugin class to
> instantiate - as of now, it verifies the class is concrete. A quick fix for
> the problem highlighted above could to add an extra condition on the Java
> modifiers of the class to ensure it will be instantiable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
