Jakub Chrzanowski
Jakub Chrzanowski
I think it'd be better if you tried the IntelliJ Platform Plugin Template: https://jb.gg/plugin-template
Thanks for reporting. When running tests, the IntelliJ Platform test platform tries to resolve the IDE location by locating the `com.intellij.openapi.application.PathManager` class. Apparently, in your case, it's not loaded from...
> I am using the workaround with JUnit 4.13.2. What workaround do you mean? Please share a minimal, reproducible project.
Changing `testRuntimeOnly("junit:junit:4.13.2")` to `testImplementation("junit:junit:4.13.2")` should solve the issue. Apparently, the test framework requires something from JUnit4 to properly work.
Thanks for reporting. I've started investigating this issue, and the problem is with the open plugin's jar file. When running the IDE with the plugin loaded, it opens `sandbox/plugin/plugin.jar` when...
The stacktrace from the first post mention `file:///Users/medvedevrv/work/Axenix/Codax.AI/codax-jb/build/reports/tests/test/index.html` tests result. What does this file say exactly?
Please upgrade to the latest IntelliJ Platform Gradle Plugin – such issues should already be addressed.
Thanks for reporting. This issue is related to the recent upgrade of `xmlutil` libraries, which bumped the `kotlinx-serialization-json` to `1.9.0`. This issue already appeared in #1885 almost a year ago,...
@Nek-12 The reason of the issue is still valid — you're providing an old version of the library to the classpath. Analyze your project's dependencies and find wich one brings...
@Nek-12 the solution based on the `buildscript {}` block is valid when you don't have custom `buildSrc` or `build-logic` involved. Otherwise, you should add that explicit dependency there, as you...