NoSuchMethodError: void KtLint$ExperimentalParams.<init>() when running spotlessCheck or spotlessApply
#1559
Comments
|
@leinardi thanks for reporting! We will look at it |
…set ids ### What's done: Additional rule set ids (available since KtLint 0.47) are now ignored, both via the `--disabled_rules` command-line argument, and via class path exclusions (Gradle plug-in). This change fixes behaviour described in #1559 with KtLint 0.47+.
|
@leinardi, found the root of the issue and working on fixing it. |
|
@nulls sure, thanks for the heads-up 👍 |
0x6675636b796f75676974687562
changed the title
NoSuchMethodError: 'void KtLint$ExperimentalParams.<init>() when running spotlessCheck or spotlessApply
0x6675636b796f75676974687562
changed the title
NoSuchMethodError: 'void KtLint$ExperimentalParams.<init>() when running spotlessCheck or spotlessApplyNoSuchMethodError: void KtLint$ExperimentalParams.<init>() when running spotlessCheck or spotlessApply
|
For the problem to manifest itself, Diktat version should be explicitly set to 1.2.4 in the Spotless plug-in configuration: spotless {
kotlin {
diktat("1.2.4")
}
kotlinGradle {
diktat("1.2.4")
}
}Diktat versions 1.2.4.1 and 1.2.4.2 are using KtLint 0.46.1 and thus are no longer affected. @leinardi, this problem has been fixed in version 1.2.4.1. Meanwhile, in case you're interested, we're releasing version 1.2.5 in the next couple of days. |
|
Hi @0x6675636b796f75676974687562, thank you for the info, I can confirm that works fine with 1.2.4.1 and 1.2.4.2. Looking forward to 1.2.5 👍 . |
|
@leinardi, version 1.2.5 has been released. So go ahead and grab the new release =) |
|
Already done, all good! 🎉 |
Describe the bug
After upgrading from 1.2.3 to 1.2.4, the following error is thrown when running detekt:
Expected behavior
No
java.lang.NoSuchMethodErroris thrownObserved behavior
java.lang.NoSuchMethodError` is thrown
Steps to Reproduce
It's happening on the default Android JUnit test:
Environment information
Possibly related to this? #1399
The text was updated successfully, but these errors were encountered: