[
https://issues.apache.org/jira/browse/FLINK-34402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815180#comment-17815180
]
Martijn Visser commented on FLINK-34402:
----------------------------------------
I don't think this is a change that Flink should incorporate like [~xtsong]
stated: we don't want Mockito in the Flink code base and recommend against it.
If you use that for your internal fork, then it's also up to you to solve any
problems that might arise because you're using something that the Flink
community discourages.
> Class loading conflicts when using PowerMock in ITcase.
> --------------------------------------------------------
>
> Key: FLINK-34402
> URL: https://issues.apache.org/jira/browse/FLINK-34402
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.19.0
> Reporter: yisha zhou
> Assignee: yisha zhou
> Priority: Major
> Fix For: 1.19.0
>
>
> Currently when no user jars exist, system classLoader will be used to load
> classes as default. However, if we use powerMock to create some ITCases, the
> framework will utilize JavassistMockClassLoader to load classes. Forcing the
> use of the system classLoader can lead to class loading conflict issue.
> Therefore we should use Thread.currentThread().getContextClassLoader()
> instead of
> ClassLoader.getSystemClassLoader() here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
