Open
Labels
Description
Describe the bug
The value of org.eclipse.jdt.core.compiler.problem.potentialNullReference preference seems to not being taken into account.
To Reproduce
Steps to reproduce the behavior:
- Create a settings.prefs file
- Add following value to the just created prefs file:
org.eclipse.jdt.core/org.eclipse.jdt.core.compiler.problem.potentialNullReference=ignore
- In VSCode, under customizations/vscode/setting, set
java.settings.urlvalue pointing to the settings.prefs file just created. - In the PROBLEMS view, any
Potential null pointer access: The variable myVar may be null at this locationerror should disappear, but does not.
Expected behavior
The configuration is obeyed and the specified warnings disappear.
Environment
- Operating System: DevContainer with mcr.microsoft.com/devcontainers/base Docker image on Debian WSL under Windows 11
- JDK version: openjdk version "1.8.0_482" as Project Java version and openjdk version "25.0.2" 2026-01-20 LTS as the JVM to be used by the Java Language Server
- Visual Studio Code version: 1.114.0
- Java extension version: 1.53.0
Additional Information
Other configuration preferences seems to be working as expected. For example setting org.eclipse.jdt.core/org.eclipse.jdt.core.compiler.problem.deprecation=ignore removes any deprecation warning.
Activity
rubensa commentedon Apr 6, 2026
As a side note, setting either
org.eclipse.jdt.core/org.eclipse.jdt.core.compiler.problem.potentialNullReference=ignore(as specified here, referenced from here) ororg.eclipse.jdt.core.compiler.problem.potentialNullReference=ignore(as is the value that the extension sets when you right click on the warning and then click onIgnore compiler problem(s)), makes no difference.rubensa commentedon Apr 7, 2026
I think this might be related to conflicts with the null analysis static code analysis feature of the extension configured via
java.compile.nullAnalysis.mode.