-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Update target platform #1614
Conversation
Signed-off-by: Sheng Chen <sheche@microsoft.com>
vscode-java-test-0.40.2023092502.vsix.zip Using this private build and the latest Pre-release of the vscode-gradle extension, which uses the build server approach should solve the problem. I tested it locally on my machine and it works. As it is mentioned in #1608, bump to JUnit 5.10.0 might cause the projects using <= 5.9.x failed to run the tests. I'm not planning to do that at this moment. From your side, is there any kind of due date or something that need the VS Code Java side to address this issue ASAP? If yes, please let me know. |
Unfortunatly, tested with the attached vscode-java-test extension and the pre-release (v3.12.2023091801) of the vscode-gradle extension I am still getting the same error as in #1613 |
Sorry forget to mention, you need to clean the workspace cache.
|
Cleaning the workspace cache, still the same result |
Could you share your VS Code settings? And maybe a screenshot of the Java Projects View ( Another difference is that I'm using Micronaut |
There is a node named Could you try to clean Java Language Server Workspace again? More details, see: redhat-developer/vscode-java#3260 (comment). Sorry for the confusion here. |
The node is named |
Still failed to launch tests? |
Yes, exactly the same error. |
I can reproduce it now on MacOS. Previously I was using Windows, which works fine. |
Is still open? Do you need help? |
Thank you @yanisderbikov. Since bumping to JUnit 5.10.0 might cause the projects using <= 5.9.x failed to run the tests. I'm not planning to do that at this moment. |
More and more users are migrating to 5.10.x The estimate time for updating the target platform will happen in May. |
Fixed in #1722 |
fix #1613
This will bump the embedded JUnit 5 to 5.10.0.