Tests are failing in Windows. I've replicated this behaviour when running the extension in Windows 10. Attempt to debug by using the gradle wrapper, as outlined in this comment: diffplug/spotless#568 (comment)

After some initial testing, it is working as expected using the gradle wrapper:

gradlew.bat spotlessApply -PspotlessIdeHook=C:\Users\Richard\Desktop\vscode-spotless-gradle\test-fixtures\gradle-project\src\main\java\gradle\project\App.java -PspotlessIdeHookUseStdIn -PspotlessIdeHookUseStdOut --quiet < stdin.txt

...with the following contents in stdin.txt:

package gradle.project;public class App {public static void main(String[] args) {System.out.println("app");}}

Using spotless-gradle version 13700cbe45344f45cbef79cbba94aec6724757f8 (latest)

Next steps: use latest spotless-gradle version in vscode, check the windows paths aren't being munged.

I've discovered the issue lies within vscode-gradle and how i'm chunking stdout based on newlines. Not sure the best approach to fixing this but at least it's fixable and not a problem with gradle or spotless-gradle.

Created a bug report in vscode-gradle to fix the streaming issues in Windows: microsoft/vscode-gradle#355

@nedtwigg This PR is pretty much ready to go. It was more work than I expected. I had all types of issues with CI, as usual haha. Integration tests (for Linux, Windows & MacOS) are now passing consistently.

Now I just need diffplug/spotless#568 merged and a new version released before I can release these changes.

I had to make a bunch of a changes to vscode-gradle including breaking public API changes. As VS Code extensions don't support beta/dev releases, this extension (vscode-spotless-gradle) is currently broken for users because of those changes.

Now published in Spotless 3.30.0.

LGTM!

Released with 0.1.0 🎉