Skip to content

refactor: use protected JUnit launch configuration API#1886

Draft
wenytang-ms wants to merge 1 commit into
mainfrom
cleanup/use-protected-vm-runner-configuration
Draft

refactor: use protected JUnit launch configuration API#1886
wenytang-ms wants to merge 1 commit into
mainfrom
cleanup/use-protected-vm-runner-configuration

Conversation

@wenytang-ms

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #1885.

Draft status

Keep this PR in draft until the latest redhat.java pre-release packages a JDT LS build containing org.eclipse.jdt.junit.core 3.15.0.

Current published JDT LS snapshot 1.61.0-202607102111 still contains org.eclipse.jdt.junit.core 3.14.300, so Java bundle resolution is expected to fail for now.

  • JDT LS snapshot repository contains org.eclipse.jdt.junit.core 3.15.0
  • latest redhat.java pre-release packages that JDT LS snapshot
  • Java plugin verification passes against the updated target
  • mark this PR ready for review

Change size

  • 2 files
  • 3 insertions, 11 deletions

Validation

mvn -f java-extension\pom.xml -pl com.microsoft.java.test.target,com.microsoft.java.test.plugin,com.microsoft.java.test.plugin.test -am verify

Currently blocked as expected by:

Missing requirement: com.microsoft.java.test.plugin 0.43.1 requires 'osgi.bundle; org.eclipse.jdt.junit.core [3.15.0,4.0.0)' but it could not be found

Replace the long-standing reflective access after eclipse-jdt/eclipse.jdt.ui#3079 exposed the launch configuration method to subclasses.

Copilot-Session: c3cd113b-dad4-4d4d-90c2-60abfd204405
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant