Description
We have a situation where there is a test client which spins off a Thread running a MockAccumulo, and then we try to use iterators that are on the classpath for that Thread. Unfortunately, they CNFE. We've traced it back, since the ReloadingClassLoader just uses the parent classloader (AccumuloClassLoader) in absence of configurations. The AccumuloClassLoader.getClassLoader uses ClassLoader.getSystemClassLoader() as it's parent, not AccumuloClassLoader.class.getClassLoader(). I believe that should preserve the way the classloaders work in the standard use cases while not breaking in any other cases.