Repository navigation
feature: Support generatesMetadataFilesAtProjectRoot #53
Description
Activity
@jvalkeal I will do a research and make it default. Changing
cmdarguments are not possible. Do you think taking cmd arguments throughrequire 'java'.setup()should be implemented? or allow functions in the setup configuration and let the user handle them if a function is passed?I don't think user should ever have full control of the command. One other thing which is absolutely something user need to controls is:
Default memory setting is fine for simple projects but will need to be changed with larger projects.
ldtlsin 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.Reacted by Srinesh NisalaI 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
.metadatadir will get mixed up.Reacted by Srinesh Nisala
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
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
jdtlshas 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