You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incompatible ASM version (9.9.0) in redhat.java 1.47.0 breaks vscode-java-test (requires 9.8.x) #1803
Hi miklosbalazsi, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Suggested Workarounds
Bundle an older ASM (9.8.x) alongside the Java Test plugin so it coexists with the newer ASM in redhat.java. See:
Update the com.microsoft.java.test.tp.target manifest to depend on a Jacoco version that supports the new ASM; monitor Update to ASM 9.8 jacoco/jacoco#1862 for the release.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
installing redhat 1.46.0 didnt fix the issue for me, not even downgading java-test extension it self, i even tried installing Jacoco 0.8.14 as some guy in issue comments suggested but that didnt work either, is this issue anywhere near fixed ?
Root cause:com.microsoft.java.test.plugin and the bundled org.jacoco.core declare a narrow org.objectweb.asm requirement, but we relied on the ASM bundle being provided by the redhat.java / JDT-LS platform. Since redhat.java's bundled ASM version varies across releases (1.46 = 9.8, 1.47 = 9.9, ...), any mismatch leaves the plugin unresolved at runtime and the test UI disappears. This is the same root cause behind #1759 and #1866.
Fix: ship the required ASM bundles (org.objectweb.asm, org.objectweb.asm.commons, org.objectweb.asm.tree) inside the extension's server/ folder and register them as contributes.javaExtensions, so the requirement is satisfied by our own bundles regardless of the ASM version the platform provides. This matches the "bundle ASM alongside the plugin so it coexists" approach suggested earlier in this thread, implemented systematically via the build allow-list.
This also decouples future Jacoco/ASM bumps from the platform's ASM version.
Activity
github-actions commentedon Oct 31, 2025
Hi miklosbalazsi, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Suggested Workarounds
VSIX: https://github.com/rgrunber/vscode-java-test/raw/refs/heads/fix-1759/vscode-java-test-0.43.1.vsix
com.microsoft.java.test.tp.targetmanifest to depend on a Jacoco version that supports the new ASM; monitor Update to ASM 9.8 jacoco/jacoco#1862 for the release.Duplicate Issue
Labels
bug test-execution high-priority investigating
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
miklosbalazsi commentedon Oct 31, 2025
I could workaroudn the problem by explicitly installed 1.46.0 redhat.java extension instead of 1.47.0
#:~/.vscode/extensions/redhat.java-1.46.0-linux-x64/server/plugins$ ls -al | grep -i asm
-rw-r--r-- 1 miklos miklos 126113 okt 31 21:07 org.objectweb.asm_9.8.0.jar
-rw-r--r-- 1 miklos miklos 73498 okt 31 21:07 org.objectweb.asm.commons_9.8.0.jar
-rw-r--r-- 1 miklos miklos 51934 okt 31 21:07 org.objectweb.asm.tree_9.8.0.jar
-rw-r--r-- 1 miklos miklos 35151 okt 31 21:07 org.objectweb.asm.tree.analysis_9.8.0.jar
-rw-r--r-- 1 miklos miklos 94559 okt 31 21:07 org.objectweb.asm.util_9.8.0.jar
jakubp03 commentedon Nov 2, 2025
installing redhat 1.46.0 didnt fix the issue for me, not even downgading java-test extension it self, i even tried installing Jacoco 0.8.14 as some guy in issue comments suggested but that didnt work either, is this issue anywhere near fixed ?
edit: this worked: redhat-developer/vscode-java#4225 (comment)
tomlaws commentedon Nov 3, 2025
VSCode is not recognizing the tests after upgrading to v1.47.0. Downgrading to 1.46.0 works again for me.
wenytang-ms commentedon Jun 8, 2026
PR #1872 should resolve this class of failure.
Root cause:
com.microsoft.java.test.pluginand the bundledorg.jacoco.coredeclare a narroworg.objectweb.asmrequirement, but we relied on the ASM bundle being provided by the redhat.java / JDT-LS platform. Since redhat.java's bundled ASM version varies across releases (1.46 = 9.8, 1.47 = 9.9, ...), any mismatch leaves the plugin unresolved at runtime and the test UI disappears. This is the same root cause behind #1759 and #1866.Fix: ship the required ASM bundles (
org.objectweb.asm,org.objectweb.asm.commons,org.objectweb.asm.tree) inside the extension'sserver/folder and register them ascontributes.javaExtensions, so the requirement is satisfied by our own bundles regardless of the ASM version the platform provides. This matches the "bundle ASM alongside the plugin so it coexists" approach suggested earlier in this thread, implemented systematically via the build allow-list.This also decouples future Jacoco/ASM bumps from the platform's ASM version.
wenytang-ms commentedon Jun 9, 2026
please install the prerelease version to verify this issue
Jakub (@jakubp03) Tom Law (@tomlaws) miklosbalazsi
jakubp03 commentedon Jul 22, 2026
i tested it on version 0.46.0 and it works