New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the compiler version included in the idea plugin is not supported #57
Comments
Also related to #38. This is happening because the artifact generated for Gradle to use is must be built against the embedded Kotlin compiler dependency which shades the 2 questions:
If it's only failing for mine I could take a look at the other plugins you have tried and see if there is something I can adopt. In the meantime I'll poke around the Kotlin supported compiler plugins and see what they do. |
serialization works, but i haven't tried with any other 3rd party plugin. I also found this issue which describes the problem https://youtrack.jetbrains.com/issue/KT-25596 |
I don't think there is anything I can do here. Unless I could somehow override both abstract methods and call the right register function in them? I think I unfortunately have to just keep point people to https://youtrack.jetbrains.com/issue/KT-25596 and telling them it's an IntelliJ problem and to use Gradle to build and run inside IntelliJ instead. |
@bnorm I have had success suppressing compile errors, but don't know if it would work in this case. So, I have a feeling you could theoretically put an Another alternative is creating an interface to force Kotlin accept the override method. Actually, is it necessary to have it be an In case you need to compile against a non-existent class, you can create a stub module creating the signatures and No-op implementations. And then using it as compileOnly. |
everything works fine when building with gradle, but when i configure Idea to use its internal JPS build system (which is sometimes faster) it seems to use a different compiler version and that does not work with kotlin-power-assert: (idea plugin 213-1.6.10-release-944-IJ6461.79)
The text was updated successfully, but these errors were encountered: