If you can’t wait for the other articles to see which other attributes you can use, then please head up to for more information. intellij īy using alternativeIdePath and pointing to our local installation of Android Studio we are telling the gradle-intellij-plugin to use Android Studio whenever we run our plugin or debug it instead of using the default IntelliJ IDE. We obviously want to test our plugin on Android Studio so to tell the gradle-intellij-plugin that we want to use Android Studio we have to add a new attribute.Īnd this is how our intellij section looks like now in our adle file. If we want to debug the behaviour of our plugin right now, what’s going to happen is that a new instance of IntelliJ will spin up an we will have to do our debugging/testing there. Our plugin as we have it now it’s only debuggable on IntelliJ IDEA CE. The only attribute that we have right now, version, it is specifying the version of the IDEA distribution that should be used as a dependency.īefore we move on, I’m going to add another attribute to the intellij section. This is the place where we will add more attributes as we need them like plugin dependencies, etc.
Secondly we have a new section called intellij. Like in any of your Android projects you can use any libraries that you want, just be careful with the libraries that you put here because this is NOT an Android project.
You can use kapt though if you need it for any kind of annotation processing (Dagger I’m looking at you). We will be coming back to this file when we start adding more dependencies and so on but for now I’m just going to focus on two things.įirst of all you can see that our dependencies uses compile instead of implementation/api, the main reason is because the gradle-intellij-plugin doesn’t support implementation or api just yet. Note keeping google() as shown below, helps you avoid errors like – “Could not find :gradle:x.y.Everything here looks really familiar because we are used to gradle in our Android projects.
0 kommentar(er)
