-
Notifications
You must be signed in to change notification settings - Fork 276
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
"Cannot resolve runtime with ideDir" #849
Comments
same warning |
Same for me, but for |
The output for me is
And also a pop-up window appears in the running IDE |
Same warning, but wait a few seconds it succeeded. Where is wrong |
same with Gradle 7.3.3
|
Same here, is this a bug? |
I saw the same issue today.
The issue got resolved by itself then I opened a terminal and type "cd $FOLDER_FROM_THE_ERROR_MESSAGE". It is no longer reproduced for me. Gradle bundled 213.6461.79, version 7.1 |
I'm getting a hard error for task
Directory This makes 1.3.1 unusable for me. 1.3.0 was unusable too, so I'm stuck on 1.2.1. Gradle 7.3.3 PS: 1.2.1 prints the same "Cannot resolve runtime" message, but the |
Hey, folks! It turned out an incorrect log level was set – it should be I've moved that logging to the |
@hsz Why is it logging Edit: Apparently, directory 'xxx' (created by gradle-intellij-plugin) contains a Linux IntelliJ distribution even though I'm on macOS (?!). Still, the log message is confusing. |
@fcurts Your case was slightly different – but fixed. Thanks for reporting it in a separate issue! |
For the record, the "Only one instance of PyCharm can be run at a time." message I had can be fixed by adding to build.gradle:
However if your plugin has any settings, it's not recommended to keep this in release builds. |
Using plugin version 1.3.0 with Gradle 7.3, when I'm building my plugin I'm getting the following output during the
buildSearchableOptions
task:The path does exist, and in the end the build does succeed.
I'm also seeing this error during the same task:
Since the build succeeds after this, I don't know what to make of it.
Should I just ignore those errors? Will my plugin be built but incorrectly so?
The text was updated successfully, but these errors were encountered: