Björn Kautler

For me it always corresponds to the current version. Maybe you can set that file's path via some environment variable or similar if that is really the file used for...

From a quick look at the changes between 0.25 and 0.26 my guess would be that it might maybe be caused by the switch from Gradle IJ plugin v1 to...

Also in 0.26.0 the folder and jar are called `plugin...` and no longer `ktlint...`, maybe that could also make problems?

Ah, having a closer look I agree that the problem might more likely be caused by the `ktlint` update. The version updated `ktlint` from 1.4.1 to 1.5.0. This updated Kotlin...

Yes, confirmed, if I install 0.26.0 and exchange the `ktlint-lib-all.jar` with the one from 0.25.0, the error is gone, but the problem with the outdated ec4j and thus empty values...

As described, I don't think anymore that the changed packaging is the problem, but the shaded classes in the kltint all jar which behave differently in 1.5.0 opposed to 1.4.1.

> But what about my other remark? As far as I can see that issue is only about wrong error message which complains about missing `bin/idea.properties` while it searched for...

Just for completeness sake: > Given this comparison I would not expect that shading to be a problem. Of course, the problem can still be caused by having different files,...

> Using a non-default installation path for the IDEA seems to be a common demoninator. Noone had a non-default installation path as far as I remember. I do not have...

Ok here, it seems to be influenced by some other plugin I have installed. I tested with a fresh settings directory with only the ktlint plugin and it worked. Then...