We have created a minimal patch based on legacy so that people in need can apply it.
Please add as necessary, create a more appropriate commit and merge.
There is no problem if you leave it as it is.

try{
}catch(~Exception e) {  <=Add!
}catch(~Exception e) {  <=Add!
}catch(~Exception e) {  <=Add!
}catch(~Tthrowable e) {
}

For Java, If want to separate logs, just add them in exeption level order.

I'm having deja vu.
(In another commit, I feel like I had a similar story with randomnicode and fxthomas...)

• The reason why the exception design of Jaudiotagger is high abstract is that it is a specification that reflects the product characteristics.
• It's not laziness that JaudiotaggerParser has a huge try block, it should be (Logging aggregation).

I think this way.

• If it's a regressive repair, having a test is not ''urgent''. Because it have a very long track record already. Of course, there should be tests. But it doesn't exist in legacy, and it's quite difficult to achieve. If realized, it will overlap with the work of the Jaudiotagger project.
• After applying this PR (that is, after reverting to the traditional implementation), any further exception design change requires valid explanation and testing. Because a defect track record has already been created.

So, I think it's okay if you include this PR simply when you release 10.6.1.
After that, you need to be alert when a similar PR comes.