Repository navigation
Bundle startup failed #1796
Copy link
Copy link
Closed
Description
The latest vscode-java build embeds org.objectweb.asm 9.9.0, so vscode-java-test extension needs to update its dependency in future release.
Language Support for Java.log
I could reproduce, logs show:
org.osgi.framework.BundleException: Could not resolve module: com.microsoft.java.test.plugin [117] Unresolved requirement: Require-Bundle: org.objectweb.asm; bundle-version="[9.8.0,9.9.0)" Unresolved requirement: Require-Bundle: junit-jupiter-engine; bundle-version="5.4.0" -> Bundle-SymbolicName: junit-jupiter-engine; bundle-version="5.11.0" junit-jupiter-engine [101] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.jdt.junit5.runtime -> Bundle-SymbolicName: org.eclipse.jdt.junit5.runtime; bundle-version="1.1.300.v20231214-1952"; singleton:="true" org.eclipse.jdt.junit5.runtime [114] Unresolved requirement: Require-Bundle: junit-jupiter-engine; bundle-version="5.4.0" -> Bundle-SymbolicName: junit-jupiter-engine; bundle-version="5.11.0" Unresolved requirement: Require-Bundle: junit-jupiter-params; bundle-version="5.4.0" -> Bundle-SymbolicName: junit-jupiter-params; bundle-version="5.11.0" junit-jupiter-params [103] Unresolved requirement: Require-Bundle: junit-jupiter-params; bundle-version="5.4.0" -> Bundle-SymbolicName: junit-jupiter-params; bundle-version="5.11.0"The latest vscode-java build embeds org.objectweb.asm 9.9.0, so
needs to be updated to relax the constraint. The previous release included 9.8.0 so it worked.vscode-java-test/java-extension/com.microsoft.java.test.plugin/META-INF/MANIFEST.MF
Line 43 in e3eb3bd
org.objectweb.asm;bundle-version="[9.8.0,9.9.0)", Can you please open a ticket in https://github.com/microsoft/vscode-java-test/issues?
Reactions are currently unavailable
Activity
github-actions commentedon Oct 9, 2025
Hi Hyeon-hak Kim (@ooMia), 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.
The
com.microsoft.java.test.pluginbundle is failing because its MANIFEST pins org.objectweb.asm to “[9.8.0,9.9.0)”, but the new vscode-java embed uses ASM 9.9.0. To fix:java-extension/com.microsoft.java.test.plugin/META-INF/MANIFEST.MF. For example:vscode-java-testextension so it can resolve ASM 9.9.0.High-confidence reference:
• Title: “Test UI does not load nor are tests found in Test Explorer”
• Problem:
org.jacoco.corebundle pinned ASM to “[9.6.0,9.7.0)” and failed after ASM was bumped to 9.7.x.• Solution: updated MANIFEST to widen the version range.
URL: https://github.com/Test UI does not load nor are tests found in Test Explorer #1688
Other references with low confidence
• Title: “JDTLS attempts to start fragments”
• Unrelated to the Java Test plugin, but also shows OSGi bundle resolution failures.
URL: JDTLS attempts to start fragments eclipse-jdtls/eclipse.jdt.ls#2762
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!
fbricon commentedon Oct 9, 2025
the problem is jacoco imposes that 9.8.0 constraint. But a new jacoco release that should fix it is pending, see jacoco/jacoco#1965
ooMia commentedon Oct 9, 2025
got it, thanks for the information :D