Open adehad opened 5 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
If you think this issue should stay open, please remove the O: stale π€
label or comment on the issue.
@nvuillam (bump to keep alive)
@adehad reopened :)
Sorry, it's hard these time to find available time :(
Completely understand don't worry
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
If you think this issue should stay open, please remove the O: stale π€
label or comment on the issue.
Comment to un-stale
Same problem here.
Thanks for your patience... it will be solved once I'll find a way to call newest npm-groovy-lint version , which is shipped as ES Module, from the Vs Code Extension :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
If you think this issue should stay open, please remove the O: stale π€
label or comment on the issue.
Up
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
If you think this issue should stay open, please remove the O: stale π€
label or comment on the issue.
Uuuup π
Hi there,
groovy-lint as the VSCode extension used to work fine on my machine can't narrows exactly when it broke but I last used it successfully in March 2024.
However, a recent change has me seeing the following error appear in a console window:
The full log I see on the VSCode extension I see is:
My guess would be that the
"jar"
file is not getting escaped in quotes in the command itself. Additionally it appears like there is mixed path separators (not sure if that would be a problem, but might not hurt to fix too)Apologies for raising this here instead of npm package which it looks like is the source of the issue.