Bug in RemoveUnusedImportsStep (Windows only?)
See original GitHub issueIt seems that despite this workaround, the Windows related bug in google-java-format’s removeUnusedImports method is still able to negatively affect Spotless, as demonstrated when one tries running ./gradlew test
against a75639f8bb637bd2caa221d18ae5d1e502b0da72, 601cff2d4987650f81aa2b7bd53c26bdd35fade3 and 8019dfe94d486bc856bbd1dfe06da7eb018aa2d0 on a Windows machine.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
removeUnusedImports fails on Java 17 #871 - GitHub
If you are submitting a bug, please include the following: summary of problem Spotless fails when running on Java 17. It seems that...
Read more >560631 – "Remove unused imports" does not work (anymore)
In brief: Clean Up > Eclipse [built in] does NOT "Remove unused imports" is Save Actiopns > Organize imports is NOT checked! This...
Read more >262268 – IDE hang when saving a file
Remove unused imports 4. Organize imports I have run across this issue dozens of times, but I can't figure out exact repro steps...
Read more >Any reason to clean up unused imports in Java, other than ...
When you're bugfixing or maintaining piece of code ( or only reading it ) it is ... For eclipse i use this: window...
Read more >Download - Recoder
Step 1: Download the current RECODER distribution. ... fixed bug [ 1988780 ] - Unresolved references using external(bytecode) enums; fixed bug [ 1988746...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, I see! Thank you for your thoughtful and insightful answer, I better understand now why you closed it in the first place, and I feel more confident in re-opening it myself now. 😃
FYI I’m re-opening it as I intend to amend
GoogleJavaFormatStep#fixWindowsBug
in the near-ish future to run only when the google-java-format version is set to 1.1, as the bug has already been fixed in master and thus won’t be around in 1.2.Done in https://github.com/diffplug/spotless/pull/73!