You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jdtls has an option which can be passed by using -Djava.import.generatesMetadataFilesAtProjectRoot=false. This is the default i.e. vscode uses thought they provide an option so that user can change it.
Describe alternatives you've considered
Think there's none unless you somehow try to override whole command launching jdtls.
Additional context
No response
The text was updated successfully, but these errors were encountered:
@jvalkeal I will do a research and make it default. Changing cmd arguments are not possible. Do you think taking cmd arguments through require 'java'.setup() should be implemented? or allow functions in the setup configuration and let the user handle them if a function is passed?
Default memory setting is fine for simple projects but will need to be changed with larger projects. ldtls in vscode quite often crashes and then it will propose to change memory settings. It'd be nice to have a generic way to modify some settings from a main config.
I was looking to just PR this little change but realised that obviously it needs to go in with #54. Once metadata moves out from a project directory into a shared workspace directory, that workspace needs to be unique as .metadata dir will get mixed up.
Did you check the docs?
Is your feature request related to a problem? Please describe.
Project metadata should not be generated inside a project.
redhat-developer/vscode-java#618
https://devblogs.microsoft.com/java/say-goodbye-to-project-files-in-1-1-0/
Describe the solution you'd like
jdtls
has an option which can be passed by using-Djava.import.generatesMetadataFilesAtProjectRoot=false
. This is the default i.e. vscode uses thought they provide an option so that user can change it.Describe alternatives you've considered
Think there's none unless you somehow try to override whole command launching
jdtls
.Additional context
No response
The text was updated successfully, but these errors were encountered: