fix: Qualified name in catch clause resolved incorrectly (noclasspath)

[slarse]

This is a test case to reproduce #3372

I haven't yet had the time to look into solutions.

update fixes #3372

[slarse]

It appears as if using the closest match (if available from TypeBinding.closestMatch(), it's null sometimes) at least lets you resolve the correct readable name. I'll try some stuff with that.

[MartinWitt]

Hi,
if you mark your test with @ignore("UnresolvedBug") the CI will check that the test fails and be green afterwards.

[slarse]

Hi!

Based on the contributing guidelines, I thought that was supposed to be used if you want to submit just a failing test case? I intend to try to solve this problem, I just haven't had the time to look into it yet.

[monperrus]

just pushed a fix to your branch, let's wait for CI

[slarse]

@monperrus Looks like it solved the problem? CI failure seems unrelated.

[monperrus]

unwip-ed, @nharrand ping