Add support for JDT Debbuger and Test Infrastructure?

Today, the VSCode Java suite of extensions use only the JDT's Language Services. Debugging, Testing Infrastructure, and other miscellaneous abilities (such as project view) are done by Microsoft's Helper extensions.

While I have no disdain for the Microsoft extensions, I believe we should unify the experience across the full Eclipse IDE and VSCode. That is, the default debugger and test runners should be the one that is natively used by the Eclipse IDE, communicated to VSCode via the Debug Adapter Protocols and Test Protocols.

Why, you might ask? Mainly to unify the experience. Most VSCode Extensions do the same:

Microsoft's own C# Dev Kit uses the same debugger and internal engine as Visual Studio for debugging and running tests.

Oracle's Java Extension uses the same Debugger and Test Infrastructure as NetBeans, communicated to VSCode via LSP and DAP.

Also, the Java Debugger by Microsoft doesn't use DAP, it uses its own custom solution, and the Java test extension produces garbage outputs when running tests, rather than having parity with CLI.

Would be neat to have one unified experience across both the native Eclipse IDE, and VSCode.

Thank You.

L’issue ne nomme aucun fichier, test ou point d’entrée. Il faut donc d’abord clarifier le périmètre de l’intégration du débogage et des tests JDT avec VSCode. Examinez les responsabilités de l’extension Java existante et de Microsoft helper-extension, puis identifiez les limites pertinentes entre Debug Adapter Protocol et Test Protocol. Le travail est terminé lorsqu’un plan d’implémentation défini pour le débogage unifié et l’exécution des tests, avec parité avec les expériences Eclipse et CLI, est disponible.