Nice catch.

How did you find it?

Please review CI failures, CI must be green.

We probably need to add such imports to forbidden

Instead of referencing of some old issue.
Make prefix "Pull #17876: ..... " As this some sort new problem. No new issue creation is required, we will reuse Pull.

@romani thanks!

re: CI failures - looks like my own stupid mistake. I misread the commit message instructions, and (wrongly!) thought they referred to the commit message subject, not the entire commit message.
CI is running now, hopefuly I got it right this time. CI has passed.

re: marking it with "Pull #17876:" - done.

re: forbidding such imports - it looks like the import-control-test.xml was supposed to do that, let me take a look.

forbidding such imports - it looks like the import-control-test.xml was supposed to do that, let me take a look.

Yes, please. I will be awesome to firbid all old junit classes, I surprised they are still available in class path

forbidding such imports - it looks like the import-control-test.xml was supposed to do that, let me take a look.

Yes, please. I will be awesome to firbid all old junit classes, I surprised they are still available in class path

Looking in to it.
Seems like there are some mistakes in the import-control-test.xml. No rocket science there, but there's some finiky work to fix it. I'll open a separate issue/PR for it.

Looking in to it. Seems like there are some mistakes in the import-control-test.xml. No rocket science there, but there's some finiky work to fix it. I'll open a separate issue/PR for it.

I take back my assessment of import-control-test.xml. It seems that the main issue isn't that configuration, but the fact that a lot of test classes just suppress the Import Control check.
In any event - I'm working on it.
Will open a PR detailing all the issues I find once I get it sorted out.