-
Notifications
You must be signed in to change notification settings - Fork 13
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
Update to support 2024.2 #132
Conversation
- Replaced build.gradle.kts to new template from https://github.com/JetBrains/intellij-platform-plugin-template/blob/main/build.gradle.kts due to migration of org.jetbrains.intellij to org.jetbrains.intellij.platform - updated gradle to 8.10 - updated jvm to 21
@Digity101 Can u merge the changes from the main branch to this, I had updated the workflow file. |
@Digity101 This issue came up when publishing the plugin. Not sure why plugin verifier didn't catch such kind of issues.
|
Idk how to address the :verifyPluginProjectConfiguration issue. In build.gradle.kts, there is Removing the implementation gives a compile error, and changing the implementation to compileOnly gives a runtime error (java.lang.ClassNotFoundException: kotlinx.coroutines.swing.SwingDispatcherKt). Changing the I am inexperienced with IntelliJ plugin development, Gradle, and Kotlin coroutines so I might have missed some obvious solution |
Hi @Digity101, Actually this might not have been the actual issue for release failure, Its
I will try uploading the plugin manually for now for v0.7.30 |
Plugins for JetBrains IDE version 2024.2+ needs JVM 21 and a migration of the Gradle IntelliJ Plugin (1.x) to IntelliJ Platform Gradle Plugin 2.0
For the migration to IntelliJ Platform Gradle Plugin, the
build.gradle.kts
file is replaced by a newer version from the templateFurthermore, to support JVM 21, Gradle is also updated to the latest version (8.10).
It should require more thorough testing on all features, but building the plugin and loading in the zip works on IntelliJ 2024.2. Furthermore, it can load a problem through competitive companion, create a test case and execute the test case with alt+x.(Running with AutoCP from context menu is greyed out though)