Package error not reported with "java.jdt.ls.javac.enabled":"on"

Describe the bug
When using "java.jdt.ls.javac.enabled":"on" on a unmanaged project, if the package does not match the folder hierarchy, no error is reported in VSCode interface

To Reproduce

1. Unzip Demo25-javac-on.zip
2. Open folder ... Demo25-javac-on
3. Open file foo\bar\ex02.java -> The package is incorrect (bar instead of foo.bar) but no error is reported
4. File ex01.java has the correct package
5. File ex03.java has no package (compact source file)

Expected behavior
A package error should be reported for ex02.java and ex03.java . In fact, the class file are not placed in the correct folders in the workspace cache folder (see left side of the picture below). When javac is on, the class are placed in folders according to the package declared in the java file instead of the original folder hierarchy. So since the class file matches the package, no package error is reported. The correct behavior is to keep the class files in the same folders of the source java files like when javac is off (right side of picture below)

Screenshots

Environment

• Operating System: Debian 13
• JDK version: 25
• Visual Studio Code version: 1.121
• Java extension version: 1.54.0

Additional Information
Maybe it is a problem in the JDT-LS from Eclipse?

Descomprime Demo25-javac-on.zip y reproduce el problema con "java.jdt.ls.javac.enabled":"on" comparando foo\bar\ex02.java con ex01.java y ex03.java. Inspecciona cómo se generan los diagnósticos de paquetes y las rutas de archivos de clase de workspace-cache, y verifica después que ex02.java y ex03.java informen de errores de paquete y que las clases almacenadas en caché conserven sus carpetas de origen.