-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Retrieving Node binary location #213
Comments
I currently got a high fever from the booster but I think if you just change to The current roadmap is pretty much merging the old PRs, fixing the old bugs, fixing some more critical bugs, opening up the internal classes, and then starting to look into the worker api / shared build services. |
Works like a charm! Take care! Should this issue remain open for the 'nicer way'? Or is closing more appropriate. |
I'll fix this in |
This was fixed in |
To allow reporting code to Sonar we used:
to determine the Node binary.
Since version 3.2.0 of the plugin this no longer works (I think it stopped working due to 98f7bdc).
I'm aware that the code snippet above is using the plugin internals. So I'm wondering whether there is a better way to retrieve the Node binary so we can correctly inform Sonar.
Thanks in advance!
The text was updated successfully, but these errors were encountered: