Fixed circular dependency problem that with certain load-orders could not be solved by Spring
Title says it all. It's a bit weird how spring does that unfortunately. Maybe I'll make an issue with them in the future. The load order differences is probably related to using a URLClassLoader (maven, unit tests, intellij etc) vs a JarClassLoader (running a JAR)