title: After restarting, Intelli-J shows no Errors until I compile, and then 100 Errors
body: <p>I am trying to use several modules written by a co-worker of mine (who is currently on vacation). I know the modules are working, because my code that relied on them was ALSO working.</p>
  
  <p>But my computer had to restart after it froze up, and now when I go into my code everything is broken, and it appears that Intelli-J forgot my dependencies.</p>
  
  <p>After a lot of fiddling, I decided to recheck everything out from git, reimport all the modules, etc. etc. But it isn't helping.</p>
  
  <p>For example, "Error:(123, 15) java: package MPD does not exist" is one error I am getting, but I can jump to the line calling MPD and "go to declaration" and see it just fine! Intelli-J knows where the source is, and there is no red squiggly line indicating there's a problem in the editor itself.</p>
  
  <p>What on earth is going on?  Did I somehow forget a step in importing modules (I imported them the same way, I thought, and added their dependencies wherever the editor said I needed to).   Or is Intelli-J itself somehow corrupted after that restart? How can I fix this?  I'm on day 2 of banging my head on this problem....</p>
  
  <p><strong>Edit:</strong> My current checkout from git has at least progressed a bit.  It turns out all my manual imports were incorrectly labelling the source as a "resource".  Manually setting most modules to correctly label "source" has gotten me further. Now I just have to figure out why it doesn't know what JUnit is anymore.  "Error:(3, 1) java: package junit.framework does not exist".  There's a few packages I haven't labeled as source yet, though, so maybe that'll fix it.</p>
  
  <p><strong>Edit:</strong>  Nope, labeling everything correctly as "source" or even "test" doesn't change my errors at all.  I can confirm that the Editor knows where the source for the various JUnit stuff, like TestCase, but the compiler swears up and down it doesn't exist. Different error, same flavor.  The JUnit references live in one of the modules, and I can confirm that if I do "mvn install" from the command line for that module, it compiles just fine.</p>
  
  <p><strong>Edit:</strong>  I can SEE Junit 3.8.1 and 4.4 in my library list, and the jar file exists where it says it should. </p>
  
  <p><strong>Edit:</strong> Different Java versions (oracle 7 vs 1.7 open jdk) do nothing.  I also tried excluding all the tests from compilation (at this point I'm desperate), but I seem to have to do it one at a time and there are a LOT of them, so I've given up that angle of attack.</p>
  
  <p><strong>Edit:</strong> Invalidating the caches and restarting does nothing at all, still getting the JUnit error.</p>
  
  <p><strong>Edit:</strong>  <em>sigh</em>  I excluded every single JUnit based class from compilation, finally.  And now I have gone full circle: "Error:(34, 15) java: package MPD does not exist".   So marking the files as source wasn't a real fix, it just delayed or hid the compilation errors.  I'm running out of random stuff to try....</p>
  
  <p><strong>Edit:</strong> I've nuked it from orbit again and got a fresh copy of my project and marked the things as source that gets me past the first compiler errors.  This time, I looked around in the dependency list, and saw that Junit was listed as only being "test" and not "compile".  Okay, I'll mark it as "compile" in all of these dozens of projects and see what happens. It is definitely getting rid of the Junit errors, one by one. </p>