Sebastian Schuberth

> I would argue this is intended behaviour. I was fearing so 😉 This makes enabling of auto-correction for only a single / few formatting rules really cumbersome as you...

I'd definitely like to see this getting merged.

I'm also seeing this wehn trying to do ``` mockkStatic(System::class) every { System.exit(any()) } just runs xsbt.boot.Boot.main(command) unmockkStatic(System::class) ``` which loops with this stacktrace: ``` getDeclaredMethod:2669, Class (java.lang) [2] allowSecurityManager:194,...

This probably is related to https://github.com/mockk/mockk/issues/191.

> Just creating a failing test first. I'm not sure what the cause is, or how to fix it. Actually, all tests in this PR seem to pass!?

Can you please share a stacktrace, or a real value for the `` placeholder?

> There is no stacktrace: the error is not fatal and the analyzer continues Have you tried `--stacktrace` which also lists suppressed exceptions?

Could be a very similar problem to #7523 or #7543.

> I tested with [311ab74](https://github.com/oss-review-toolkit/ort/commit/311ab74142ecd908b3ad81a0911b31a1ee0887a1) but the problem persists That's expected. It's just that a (probably) similar issue was fixed for another package manager (CocoaPods).

@aames-cls, can you please share the project you're using for testing?