title: Analyse complete project at once with SonarLint - Analysis file by file yields incomplete results
body: <p>I'm evaluating SonarQube 5.4 with SonarLint eclipse plugin.</p>
  
  <p>SonarQube as well as the plugin are set up and are running. But now I'm pretty confused how SonarLint is supposed to run in 'connected mode':</p>
  
  <ul>
  <li>SonarLint is connected with SonarQube and is bound to the corresponding project. But some issues are only shown in SonarQube. It was my understanding SonarLint should be able to identify issues like <code>Malicious code vulnerability - May expose internal representation by incorporating reference to mutable object</code>. But it does not. SonarQube does.</li>
  <li>When analysing a single file with SonarLint, there are a lot of debug messages in the SonarLint Console like <code>Class not found in resource cache : org/company/project/CommonSuperClass</code>. But even worse: <code>Class not found in resource cache : java/lang/Class</code>. Is it supposed to do that?</li>
  <li>We are specifically interested in highlighting the issues introduced by developer. SonarQube is connected our repo and does a nice job in <em>blaming</em> the committer. But it seems there is no way of showing <em>my own issues</em> in sonarlint. </li>
  <li>I'd like to run the SonarLint analysis at a time of my choice, so I decided to deactivated "Run SonarLint automatically". But it seems I can only analyze files manually, not packages or projects. Am I missing something again? I do not want to click on every one of my ~2000 files and analyze it by hand. </li>
  </ul>