Exceptions are buried in the log file.

I turned on the java tooling in vscode for a flutter project and received the following error:

Failed to configure project sounds

When I googled the error I found a github issue that suggested I should open the java log file where I found:

java.lang.Exception: Could not set the project description for 'sounds' because the project description file (.project) is out of sync with the file system.

I shouldn't have to dig into a log file to find the actual error. vscode-java should be showing the exception description in the vscode problems window.

Version: 1.54.1
Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8
Date: 2021-03-04T22:38:50.094Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Linux x64 5.8.0-44-generic snap

Language Support for java by redhat: v0.76.0

java --version
openjdk 11.0.10 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+9-Ubuntu-0ubuntu1.20.10)
OpenJDK 64-Bit Server VM (build 11.0.10+9-Ubuntu-0ubuntu1.20.10, mixed mode, sharing)

Ubuntu 20.04

Could not set the project description for 'sounds' because the project description file (.project) is out of sync with the file system.

El issue no menciona archivos fuente, pruebas ni puntos de entrada. Reproduce el fallo de configuración del proyecto con las herramientas de Java en VS Code y, después, sigue cómo llega ese error a la ventana Problems; se considera terminado cuando allí se muestra la descripción de la excepción, en lugar de aparecer solo en el Java log.