Organize imports fails to work
See original GitHub issue[provide a description of the issue]
Environment
- Operating System: macOS 10.13.3
- JDK version: 1.8.0_112
- Visual Studio Code version: 1.22.2
- Java extension version: 0.22.0
Steps To Reproduce
Shift
+ Alt
+ O
fails to organize imports but if I write in the configuration like:
"java.saveActions.organizeImports": true,
it works when I use Command
+ S
, but still not work for the Shift
+ Alt
+ O
combination.
[attach a sample project reproducing the error]
attach logs
Current Result
Expected Result
Additional Informations
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6
Top Results From Across the Web
Why "Source > Organize Imports" does not work in Eclipse?
Scenario 1: The package that is to be identified by Eclipse may not be in your project classpath. Scenario 2: Eclipse is not...
Read more >Organize imports does not work in accordance to preferences
When I adjust "Organize Imports" settings (add or edit) Eclipse does not allow to enter something like regular expression, it forces me to...
Read more >prettier-plugin-organize-imports - npm
A plugin that makes Prettier organize your imports (i. e. sorts, combines and removes unused ones) using the organizeImports feature of the ...
Read more >Eclipse Shortcut to get rid of all unused Imports in a Java file
It's better to use the “Organize Imports” feature of Eclipse IDE to remove multiple or all unused imports statement. For using this from...
Read more >VS Code tips — Organize imports - YouTube
Today's VS Code tip: Organize Imports Use the organize imports command to sort imports and remove unused ones for JavaS … Show more....
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 Free
Top 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
Well, yeah kinda 😉
If you open a single java file from vscode, it still won’t work.
But, last night, we merged Microsoft’s new patch to improve standalone java files support. So, with the latest CI build, if you open the folder containing that java file (including all the folders from its packages), then you’ll get full java support: organize imports, compilation errors, the whole shebang. No more “incomplete classpath” warning.
This will be part of the next release, around Dec 15th.
Hey all… any update on this?