Verify whether upcoming when clause parser breaks any feature

[Eskibear]

New when clause parser introduced in microsoft/vscode#175540

Please verify if there's any potential breakage in each extensions, using latest insiders.

[github-actions]

Hi Yan Zhang (@Eskibear), 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.

Verify your Java extensions against VS Code Insiders and inspect any failures in when-clause parsing:

• Install the latest Insiders build and enable only your Java extensions (e.g., vscode-java, vscode-java-debug, vscode-maven).
• Run key workflows:
  • Code completion, semantic highlighting, refactoring
  • Debugging and call-stack navigation
  • Type Hierarchy, Project Explorer, launch configurations
• In Developer Tools (Help > Toggle Developer Tools), look for JSON parsing errors around when contexts in package.json.

High-confidence reference:

• Show Type Hierarchy breaks in vscode-insiders: activation broke due to publisher ID change—use getExtension('vscode.java') with fallback. See solution:
  Show Type Hierarchy breaks in vscode-insiders redhat-developer/vscode-java#2524 (comment)

Other references with low confidence

• Add syntax highlighting for var keyword in Java 10: tests grammar changes in Insiders. Add syntax highlighting for var keyword in Java 10 redhat-developer/vscode-java#604 (comment)
• Jump to source when clicking call-stack info: Insiders feature testing for vscode-java-debug. Jump to source when clicking the call stack info in debug console vscode-java-debug#506

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!

[Eskibear]

Closing as completed. This was a pre-release check for VS Code 1.77, and no Java extension breakage was found.