![]() ![]() For example, you downloaded a project from somewhere like github with last update a few years ago, and want to know the Android Gradle Plugin Version to decide which version of Android Studio to use to open the project in the first place. However, in some cases it is not so convenient to import the project into Android Studio, let it gradle sync and then navigate to that place to view the versions. In fact, from his screenshot, both can be seen in the same place in Android Studio and they in general are different values. His answer then shows how to find the Android Plugin Version (you may also see this called Android Gradle Plugin Version on some versions of Android Studio) from within Android Studio.Īdam Johns' answer, on the other hand, shows how to find the Gradle Version. The former is the build system itself, the latter is the plugin to the build system that knows how to build Android projects Use '-warning-mode all' to show the individual deprecation warnings.Make sure you don't confuse the Gradle version with the Android plugin version. If that, you will find this warning : Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. But avoid this thing, if the version really old. This way we prevent downloading the gradle again and again. Change this entry: distributionUrl=http\:///distributions/gradle-6.1.1-all.zip In your Opened project, navigate Android Studio's project tree, open the file gradle/wrapper/gradle-wrapper.properties. Go to : C:\adle\wrapper\dists, here you see the versions allready installed, remember the latest version, assume it is gradle-6.1.1-all.zip. First You have to know the gradle version that already installed in your machine. To prevent this download there is one trick. ![]() But, If your particular project gradle version not match with the gradle version that already installed in the machine, the gradle sycn want to download that version. Now all the Gradle data can be found in your HOME directory, usually located here (in this case on Windows): # tree -L 2 $USERPROFILE/.gradle/ | tail -n +2Īssume, you have installed the latest gradle once. ![]() Now, all you need to do is to select: (o) Use local gradle distribution.ĪS will then tell you it found your local Gradle paths: Perhaps because Android Studio (AS) is constantlyĬhanging/evolving? Nevertheless, the procedure is this simple.Īssuming you have already installed Gradle in a suitable directory, mean that you probably also defined an environment variable for GRADLE_HOME, if not define it now, and restart AS.įor my example: GRADLE_HOME=C:\Gradle\gradle-5.2.1įile > Settings > Build, Execution, Deployment > Gradle I'm not sure why there are so many contorted descriptions of doing It's better to provide an option to choose local gradle installation dir or. Since it's so slow when download gradle distrbution within Android Studio.(For Android Studio 3.3.1, which use gradle ~/.gradle/wrapper$ tree -L 4 Each version of Android Studio might use different gradle version, thus might need to repeat this process once, when Android Studio is upgraded.That means you didn't kill the previous download process, kill it first, then remove blank project, then create a new project to confirm again. After restart Android Studio & creating blank project again, if you see it says waiting for other process to download the distribution.And starts to sync dependencies, indexing, and build.It will uncompress gradle in the the same dir.Į.g.Then it shouldn't need to download gradle again. ![]() And copy the download file there instead.Į.g.Kill all the related android processes.Find the download process, by android-studio.Then it will create the hash, and start to download gradle.Į.g.To download manually, need to download to the exact sub dir named by the hash. (recommended)Īndroid Studio will download gradle to sub dir named by a hash. Solution B: Download gradle distribution manually for gradlew. And, with this solution, each time open project, android-studio will ask to confirm whether to use gradlew instead, it's kinda annoying.I tried, it works, though this is not suggested for gradle use in general.Solution A: Use location gradle, and delete gradlew related files. So, I would add a summary with missing details to save the unnecessary time wasted, in case others encounter into the same issue.) (There are 2 solutions mentioned in existing answers that might work, but the preferred one - manually download gradle for gradlew, is lack of essential details, and cause it fail. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |