-
Notifications
You must be signed in to change notification settings - Fork 6
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
Use Gradle jdk to run MOE build #8
Conversation
@Berstanio Could you give this a try and see if this solves the "Module SDK not configured or it's not a valid JDK" issue? |
#7 already fixed the issue for me. But I will check this changes out too |
FYI this will break the plugin with MOE 2.0 though because it won't set the GraalVM as the module SDK. I'll try to figure out how to put #6 into this. Currently this update will force setting the module SDK to MOE everything you resync the gradle project. This need to be disabled for MOE 2.x to allow user to change the module SDK. |
The changes work fine for me! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works good for me!
* commit '87d220fbcc52dab8517e67d67520658e1cb6a2a4': Set graalvm as sdk when possible # Conflicts: # src/main/java/org/moe/idea/sdk/MOESdkType.java # src/main/kotlin/org/moe/idea/model/impl/MOESdkPropertiesImpl.kt
…d as module SDK. Fix SDK naming.
This uses Gradle JDK to execute build commands, so we don't need to mess around with the MOE SDK. This is particularly useful in Android Studio when you have both Android and iOS module in a single project, as the Android Studio's module settings dialog is a minified version that does not allow you to modify module JDK settings.