Repository navigation
"java.compile.nullAnalysis.mode: automatic" not inheriting settings from "java.settings.url" #4329
Description
When using the setting "java.compile.nullAnalysis.mode: automatic" the following settings are always overridden regardless of what their values in the "java.settings.url" are:
org.eclipse.jdt.core.compiler.problem.nullAnnotationInferenceConflict=warning
org.eclipse.jdt.core.compiler.problem.nullReference=warning
org.eclipse.jdt.core.compiler.problem.nullSpecViolation=warning
org.eclipse.jdt.core.compiler.problem.potentialNullReference=warning
They are always set to be warning even when the users "java.settings.url" looks like:
org.eclipse.jdt.core.compiler.problem.nullAnnotationInferenceConflict=error
org.eclipse.jdt.core.compiler.problem.nullReference=error
org.eclipse.jdt.core.compiler.problem.nullSpecViolation=error
org.eclipse.jdt.core.compiler.problem.potentialNullReference=error
I would expect when generating the projects metadata it would inherit the default values for these settings from the users "java.settings.url" instead of always defaulting to warning.
Please let me know if there is anymore information that would be helpful, thank you
Activity
fbricon commentedon Feb 3, 2026
so basically java.settings.url behave like Eclipse's workspace settings: they're applied unless a project overrides them in its .settings/*.prefs. Is this your case?
kiihneC commentedon Feb 10, 2026
The issue ended up being that the eclipse buildship plugin has default values when generating these settings that are always applied (setting these to be warnings instead of errors), it does not care what your java.settings.url settings have in them. The problem is with eclipse buildship instead of the vscode-java extension. Thank you for your help