Completion fails when there are projects inside that use gradle

[plitter]

At my work we have a large project which has a maven project root, maven middle project root and maven project. At the project level there are some javascript node modules that use gradle.
I'm using YCM with the latest jdt.ls version as of writing 0.25. ycm-core/ycmd@aa1c7b7 is the commit I'm at (thanks to Boris and micbou at YCM for help with this).

https://ptpb.pw/-B6R
https://ptpb.pw/jMe1
https://ptpb.pw/Ntt3

The above are the errorlogs from ycm with debug on.

After I removed the projects that where using gradle, the completion works.

[fbricon]

I don't know what kind of settings ycmd allows (ask their team), but by default, jdt.ls has

"java.import.exclusions": [
		"**/node_modules/**",
		"**/.metadata/**",
		"**/archetype-resources/**",
		"**/META-INF/maven/**",
	],"

That prevents node modules with gradle build files in it to be imported as Maven projects. That works well for vscode.
Does ycmd override those settings?

[bstaletic]

For the record, ycmd doesn't override any jdt settings and allows users to set anything in the project specific .ycm_extra_conf.py.

[puremourning]

but by default, jdt.ls has

Is that a default in the server-side, or the VSCode client ?

ycmd does not override any settings for jdt.ls by default and I would be very surprised if any user was setting any of them using the mechanism we support to set them