You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am (or was :) ) using the grunt task in a project where the project folder contained a whitespace (I know not the best case but hey ... legacy stuff).
The sonar runner jar file path isnt quoted so the jarfile could not be accessed.
Changed the folder to a non whitespace name and everything worked again
The text was updated successfully, but these errors were encountered:
Also ran into this issue while building on cloud Jenkins instances, which will have spaces in the build path if your job names have a space. Quoting both the jar path and runner.home parameters seems to work.
Hi,
I am (or was :) ) using the grunt task in a project where the project folder contained a whitespace (I know not the best case but hey ... legacy stuff).
The sonar runner jar file path isnt quoted so the jarfile could not be accessed.
Changed the folder to a non whitespace name and everything worked again
The text was updated successfully, but these errors were encountered: