I believe the plugin was installed successfully, because I attempted to make a new Java project in eclipse 2019-09, (i.e. “hello world”) and was able to analyze with SonarLint.
Previous issues seem to suggest that this is a permissions-based issue, but I am not sure why SonarLint is attempting to access AppData Folder when my eclipse project does not point to that folder.
Looking at the stack trace, the error occurs when our Java analyzer tries to access one entry of your project classpath. This is strange to have AddData folder part of the classpath, so I would ask you to check your project classpath configuration.
To see the classpath processed by SonarLint, open the SonarLint console, then enable verbose output. When you open or modify a file, an analysis will be triggered and you should see this log:
The interesting parts for your issue are the sonar.java.libraries and sonar.java.binaries extra properties. Confirm one entry is actually C:\Users\xxx\AddData\Local\Application Data.
Then look at your project settings, to find why you have this entry:
While I did not get to implement the solution you proposed, I discovered that after remaking a JAVA project and moving classes into this new location SonarLint was able to run. Once I rebuilt my reference libraries, that’s where the errors returned.
The solution: Moving my reference libraries into my eclipse workspace folder, where my java project folder exists.