-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
this.pathResolver null on macOS #33
Comments
Hello and thank you for your issue :) |
@philippefichet can I put that path in a config file? I found this file in my previous NB installation:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//NetBeans//DTD Module Status 1.0//EN"
"http://www.netbeans.org/dtds/module-status-1_0.dtd">
<module name="com.github.philippefichet.sonarlint4netbeans">
<param name="autoload">false</param>
<param name="eager">false</param>
<param name="enabled">true</param>
<param name="jar">modules/com-github-philippefichet-sonarlint4netbeans.jar</param>
<param name="reloadable">false</param>
</module> |
I didn't understand the screenshot like that, OK.
And to fix the problem at the root I think we will have to implement the interface "org.sonarsource.nodejs.BundlePathResolver". |
Great, thank you! That workaround is working for me. |
Good news :), |
Thanks again. Happy to test any changes. |
Thank you phiippefichet and jepsar for identifying and providing a workaround for this issue. Plugin now works for me on mac as well. Much appreciated. |
I think I fixed this error in the "fix-npe-nodejs-macos" branch, but I could only use github actions to check. |
Is there a release I can test? |
No, the patch is just on a branch but I could do a build if needed |
That would be great. The only thing I should do is disable |
Here is the nbm file of the pre release with the patch. |
I'm getting
|
Thank you for your test. |
I think I have solved the NullPointerException problem. |
Your link points to a release done 13 days ago. Is it correct? |
Yes, I just re-uploaded the .nbm |
I'm able to access the plugin options now, so that's an improvement. However, I do get:
|
@jepsar Thanks again for your tests :) |
In the notifications. |
Thanks @jepsar, I managed to reproduce this mistake and correct it :). |
The text was updated successfully, but these errors were encountered: