NullPointerException in JDTMicroProfileUtils.getProjectURI

[fbricon]

jdt.ls telemetry reported this NPE:

java.lang.NullPointerException: Cannot invoke "org.eclipse.core.runtime.IPath.toOSString()" because the return value of "org.eclipse.core.resources.IProject.getLocation()" is null
at org.eclipse.lsp4mp.jdt.core.utils.JDTMicroProfileUtils.getProjectURI(JDTMicroProfileUtils.java:64)
at org.eclipse.lsp4mp.jdt.core.utils.JDTMicroProfileUtils.getProjectURI(JDTMicroProfileUtils.java:54)
at org.eclipse.lsp4mp.jdt.internal.core.MicroProfilePropertiesListenerManager$MicroProfileListener.processDelta(MicroProfilePropertiesListenerManager.java:106)
at org.eclipse.lsp4mp.jdt.internal.core.MicroProfilePropertiesListenerManager$MicroProfileListener.processDeltaChildren(MicroProfilePropertiesListenerManager.java:86)
at org.eclipse.lsp4mp.jdt.internal.core.MicroProfilePropertiesListenerManager$MicroProfileListener.processDelta(MicroProfilePropertiesListenerManager.java:96)

I can't provide any context or steps to reproduce.

[angelozerr]

I don't know if it is true, but according chatgpt:

When org.eclipse.core.resources.IProject.getLocation() returns null, it means Eclipse doesn’t know the project’s local file system path. This usually happens in one of the following cases:

• The project is closed → closed projects don’t have an accessible location until opened.
• The project hasn’t been created or opened yet → calling getProject() only gives you a handle; call create() and open() first.
• The project uses a non-local file system (EFS) → for example, remote or virtual projects. Use getLocationURI() instead, which always works, even for non-file: URIs.

The project is deleted or invalid → project.exists() returns false.

We need to take care of this usecase.