-
Notifications
You must be signed in to change notification settings - Fork 488
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
8274274: Update JUnit to version 5.8.1 #633
Conversation
👋 Welcome back jhendrikx! A progress list of the required criteria for merging this PR into |
Webrevs
|
072494e
to
233fdb8
Compare
Sorry for the force push, forgot I already submitted it as a PR. I only removed a few extraneous dependencies that got added in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned in JBS, any new third-party libraries require prior third-party license approval. And we will need to work with you on sponsoring this (as you can't contribute any third-party code under the OCA).
Speaking of which, there are more libraries added to gradle-verification.xml
than I would expect. Each one will need third-party approval, if they are required. Since this is for internal use (build / test only) and not something we redistribute, that makes it easier, although it still depends on the license for each piece.
Finally, we have some closed tests that we need to ensure aren't impacted by this, so that's one more area we need to coordinate.
We can take a look, but it won't be right away. Can you also start a thread on openjfx-dev? I'd like to gauge the level of interest in enabling JUnit 5 for new tests.
/reviewers 3 |
@kevinrushforth |
That's OK. I deleted the couple of comments I had added relating to blocks that disappeared. |
Btw, I think this should be moved to a Draft PR until the third-party issues are resolved (including any needed approvals). |
The gradle verification task failed (see the test results from GitHub Actiona). It looks like it still needs the hamcrest jars. Go ahead and add them back in (and remove the exclusion for them). |
Yeah, I noticed, I couldn't get rid of them. Apparently JUnit 4 itself is depending on them now (starting from 4.10 orso) and the Vintage engine requires JUnit 4.12+, so it is actually overriding JUnit 4.8.2 to 4.13.2 and pulls in the Hamcrest jars again. I've tried forcing JUnit to 4.8.2 and even though that works, it leads to a spam stacktrace in the logs for each test executed because it can't find something via reflection. I then tried to hide this log message, but have been unable to find any way of getting that message blocked by configuring java.util.logging that works in combination with Gradle and its daemon. So... I've sort of think this is not a fight we can win easily and have reincluded the Hamcrest jars. EDIT: Still something breaks, base is working but graphics isn't, will fix this locally and update in a moment. |
The thread on the mailinglist to gauge interest seems to have been concluded. We got 4 responses, all in favor. |
I'll look at getting the necessary approvals starting next week. It should be relatively straight-forward. |
As indicated in the JBS issue, we can now proceed with this. You will need to change the title of this PR to match the updated bug title. |
It looks like I spoke too soon. I am informed there is still another needed step. |
I was on holidays, I've updated the title. |
All tasks needed to get third-party approval are now completed. You can move this PR back to ready and the review can proceed. |
I also was able to make the (minor) changes needed to our closed build to use the As a note to other committers: Given that this is a third-party update, and that I need to integrate a coordinated closed change, I will sponsor this once it is ready. Please don't sponsor it even if it appears to be waiting for a while. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with one comment inline.
I was looking for places where JUnit 4.8.2 was still being referenced and found two more places that should be changed:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I did a CI build with the latest changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me. The tests work as expected.
This looks good. I noticed that the fix for |
@hjohn This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 50 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@kevinrushforth, @johanvos) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit ff6e8d5.
Your commit was automatically rebased without conflicts. |
@kevinrushforth @hjohn Pushed as commit ff6e8d5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I've added JUnit 5 as a test dependency and made sure that the JUnit 4 tests still work. Also added a single JUnit 5 tests, and confirmed it works.
I've updated the Eclipse project file for the base module only.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/633/head:pull/633
$ git checkout pull/633
Update a local copy of the PR:
$ git checkout pull/633
$ git pull https://git.openjdk.java.net/jfx pull/633/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 633
View PR using the GUI difftool:
$ git pr show -t 633
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/633.diff