On 7/6/2011 9:35 AM, Knut Anders Hatlen wrote:
We should, but we just shut down the engine, we don't deregister the
driver in DriverManager, so the classes stay in memory forever. It's a
bit tricky to get the old versions unloaded. Simply calling
DriverManager.deregisterDriver() in the test tear-down won't work, since
it'll only let you deregister drivers in the same class loader as the
caller, and the test framework and the old drivers are loaded in
different class loaders.
If we used DataSources for the upgrade tests would we avoid this problem
or would the autoloaded driver still get loaded?
