fix: Restrict JUnit version#1466
Merged
rubenporras merged 1 commit intoeclipse-lsp4e:mainfrom Dec 15, 2025
Merged
Conversation
Contributor
Author
|
Well, the tests are running again, be we seem to have a quite a few regressions and flaky tests :( |
Contributor
|
Thanks for the PR, I will override the checks and merge it despite the build failures. I do not know what happened to the baseline and build artifacts check to report suddenly now different contents but same versions. Neither do I know what happened so that the test execution started to fail but this PR fixes at least this problem. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should fix the current problems with the maven build, i.e.,
I restricted the JUnit Version to 5, which seems to be the fix, according to https://eclipse.dev/eclipse/markdown/?f=news/4.38/pde.md