Sonarlint 2.3 eclipse issues shown on parent project
<p>I used Sonarlint 2.2.1 with Eclipse Luna, it was working quite well but since i've upgraded to Sonarlint 2.3, nothing works like before.</p>

<p>I use Sonarlint as a standalone eclipse plugin without a SonarQube server.</p>

<p>I work on a project with this kind of structure :</p>

<pre><code>Parent
  |
  |-&gt; module1
  |-&gt; module2
  |-&gt; ...
  |
</code></pre>

<p>In v2.2.1 sonarlint show all issues of all modules even if I close or delete the parent project from project.</p>

<p>In v2.3 sonarlint, no issue is displayed on the sonarlint view.</p>

<p>If I open <code>/module1/src/main/.../SomeClass.java</code>, then the issues of the current opened class are shown in the list but not inside the opened class.
And when I double-click on an issue in the list, it opens the file link to <code>/parent/module1/src/main/.../SomeClass.java</code> which is not considered as a file in the build path.
In the path column of the issues view, the path is like <code>/parent/module1/src/main/.../SomeClass.java</code>.</p>

<p>If I open a second class, the issues of that class come feeding the sonarlint issues view list.</p>

<p><strong>If I close the parent project</strong> in eclipse, then I got an error telling me that the resources <code>/parent/module1/src/main/.../SomeClass.java</code> do not exist.</p>

<p><strong>If I delete the parent project</strong> in eclipse, the issues are shown in the open file and the value of the column path in the sonarlint issues view is correct: <code>/module1/src/main/.../SomeClass.java</code></p>

<p>Has anyone encountered the same problem?</p>