-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8347814: Make all imports consistent in the FFM API tests and benchmarks #23689
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
Conversation
|
👋 Welcome back pminborg! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
|
@minborg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
@minborg This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
|
/open |
|
@minborg This pull request is now open |
| import static org.testng.Assert.assertFalse; | ||
| import static org.testng.Assert.assertNotEquals; | ||
| import static org.testng.Assert.assertTrue; | ||
| import static org.testng.Assert.*; |
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.
Duplicate my comment: https://github.com/openjdk/jdk/pull/22827/files#r2059725341
It looks inconsistent that in some places you remove the wildcard (*) imports, while in others you add them.
By the way, where does this convention come from? I believe most of the codebase follows the import order: java → empty line → javax → empty line → other jdk packages in alphabetical order → empty line → repeat the same groups for static imports.
|
In the end, this didn't make the bar in terms of cost/benefit. For example, backporting might be impacted. |
The first LTS release to include this API will be 25, correct? It would be best to clean this up in advance, as backporting to versions 22, 23, or 24 is unlikely - just a thought. |
This PR proposes to make all imports consistent in the FFM API tests and benchmarks.
This is a follow-up PR from #22827
Passes tier1-3
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23689/head:pull/23689$ git checkout pull/23689Update a local copy of the PR:
$ git checkout pull/23689$ git pull https://git.openjdk.org/jdk.git pull/23689/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23689View PR using the GUI difftool:
$ git pr show -t 23689Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23689.diff
Using Webrev
Link to Webrev Comment