In days of old, we would execute long-running processes against jars that were overwritten nightly.
The effect of re-writing the jar files as a process was running would invariably kill the process.
The solution was to pre-load all the classes in the package and in the dependent jar files up front rather than when required.
This was done using the LoadReferencedClasses.loadClasses method.
This allowed the process to continue despite the jar files being re-written.
I am happy to say that this method of running against an often updating jar is no longer common place and so this method should not be used as a matter of course.
It remains in place (and un-deprecated) as there may arise instances where its utility may be useful.
All classes (apart from the test class) that called this method have been updated to remove the call to this method.
Description
In days of old, we would execute long-running processes against jars that were overwritten nightly. The effect of re-writing the jar files as a process was running would invariably kill the process. The solution was to pre-load all the classes in the package and in the dependent jar files up front rather than when required. This was done using the
LoadReferencedClasses.loadClassesmethod. This allowed the process to continue despite the jar files being re-written.I am happy to say that this method of running against an often updating jar is no longer common place and so this method should not be used as a matter of course. It remains in place (and un-deprecated) as there may arise instances where its utility may be useful.
All classes (apart from the test class) that called this method have been updated to remove the call to this method.
Fixes #213