Failed to get sources when debugging multi module maven project in vscode

I managed to open a multi-module maven project in VS Code and set up the launch.json correctly. I can debug the project and the breakpoints are respected in the main module. When I set a breakpoint in a referenced module, the execution will break, but I see a decompiled version of the class with the following comments:

 // Failed to get sources. Instead, stub sources have been generated by the disassembler.
 // Implementation of methods is unavailable.

I added the plugin in pom.xml for that module to generate the source from maven and the source. Then I used mvn clean install and the source code JAR was generated successfully under the target folder for the specific module.

I tried to launch the debug again, and nothing worked. I still see the decompiled version of the class.

I configured "sourcePaths" in launch.json to point to the generated source JAR and it didn't and didn't work. I tried to point to the folder, relative path, absolute path, and with/without the filename, but nothing worked.

I appreciate your help to find a resolution to this issue.

Environment

• Operating System: Windows 11
• JDK version: 1.8 and 18
• Visual Studio Code version: latest
• Java extension version:
• Java Debugger extension version:

Steps To Reproduce

1. Open Java multi module maven project in VS code and wait until its fully loaded
2. Setup the launch config to debug the project.
3. Set breakpoints in the main and the other referenced modules.
4. Start debug

[attach a sample project reproducing the error]
attach logs

Current Result

Breakpoint works only with the main module. The breakpoint in the other module works but source code is not used.

Expected Result

Breakpoint should work and source code should be displayed for all modules.

Additional Informations

I tried all possible steps to resolve this problem but nothing worked.

Comienza reproduciendo la configuración multi-módulo utilizando los pom.xml y launch.json referenciados, con breakpoints en el módulo principal y en los módulos referenciados. Investiga cómo sourcePaths resuelve el source JAR generado bajo target y, después, verifica que los breakpoints de todos los módulos muestren el código fuente en lugar de clases decompiladas.