Bundle startup failed

[ooMia]

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.

• issue from Failed to load vscode-java-test bundles (jacoco not compatible with asm 9.9.0) redhat-developer/vscode-java#4205

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

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)",

needs to be updated to relax the constraint. The previous release included 9.8.0 so it worked.

Can you please open a ticket in https://github.com/microsoft/vscode-java-test/issues?

cc Fred Bricon (@fbricon)

[github-actions]

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.plugin bundle 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:

• Open an issue (or PR) in microsoft/vscode-java-test to relax that constraint in java-extension/com.microsoft.java.test.plugin/META-INF/MANIFEST.MF. For example:

  Require-Bundle: org.objectweb.asm;bundle-version="[9.8.0,10.0.0)"
  

• After the update, rebuild and install the vscode-java-test extension so it can resolve ASM 9.9.0.

High-confidence reference:

• Test UI does not load nor are tests found in Test Explorer #1688
  • Title: “Test UI does not load nor are tests found in Test Explorer”
  • Problem: org.jacoco.core bundle 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

• JDTLS attempts to start fragments eclipse-jdtls/eclipse.jdt.ls#2762
  • 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]

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]

got it, thanks for the information :D