Suggestion
JDT.UI has a notion of "save action" - performing code manipulation on save (e.g. "organize imports"). JDT LS also supports this and it's exposed in VScode Java .
JDT LS and JDT UI implementations use different keys for same save actions. As for both the keys are part of user configs it's not feasible to change any of them thus the plan is:
- Make JDT LS support both keys for same actions
- Feed JDT LS with org.eclipse.jdt.ui.prefs from the project to enable the execution of the save action.
Community
Suggestion
JDT.UI has a notion of "save action" - performing code manipulation on save (e.g. "organize imports"). JDT LS also supports this and it's exposed in VScode Java .
JDT LS and JDT UI implementations use different keys for same save actions. As for both the keys are part of user configs it's not feasible to change any of them thus the plan is:
Community