Thanks for the reference. It might be a failure to read, but I couldn't find where it specifies that it searches the classpath in order. Only that it searches jar manifests in order.
It seems plausible that the file classloader does actually traverse the classpath in order, but it still looks like it's not guaranteed, since it's not in the spec. It may not be a huge deal, since the only impact of loading the wrong class is a flaky test, which we can easily just fix again later on. [ Full content available at: https://github.com/apache/kafka/pull/5605 ] This message was relayed via gitbox.apache.org for [email protected]
