I always appreciated what IDEA prints as the first line of the console output when you run/debug your application, or even tests. For whatever reason something switched dynamic.classpath to true (not sure what does it, maybe some plugin?) and it stopped doing it, I understand the reasoning behind it (safer for possibly too long classpaths, etc.), although I miss the output and the file mentioned in the command line (e.g. `C:\Users\Virgo\AppData\Local\Temp\classpath2.tmp`) is already gone when I want to check its content. I just put classpath printing it into my application, and I'm fine.
However, this method obviously affects some other tools. I wasn't able to enable jmockit-coverate, although I clearly had it on the classpath. I moved on, but to my surprise, when I ran some test on different computer, it started producing the coverage output! Running the test also printed the whole classpath on the first line. That's when I started to dig deeper to find out what causes this (posts like http://stackoverflow.com/questions/4853540/what-does-the-dynamic-classpath-flag-do-intellij-project-settings, but there are others).
What may be the difference causing jmockit-coverage not getting activated in the case of dynamic.classpath?