AppCode 2019.3 Help

Gradle settings

Preferences | Build, Execution, Deployment | Gradle

Use this page to configure the Gradle project settings.



Gradle user home

Use this field to specify the location of stored Gradle caches, downloaded files, and so on.

If Gradle location has been defined by the environment variables GRADLE_HOME or PATH, then AppCode deduces this location, and suggests this path as the default value.

If the Gradle location has not been deduced from the environment variables, specify it manually, or click the Browse button, and select the desired directory in the dialog that opens. Note that the value entered in this field takes preference over the environment variables.

Generate *.iml files for modules imported from Gradle

Select this option to store the generated .iml and library files in the .idea directory instead of idea.system.path.

It might be helpful in the following cases:

  • sharing the IDE-specific module settings via VCS since the .idea directory stores project-level settings. You can also opt for the gradle-idea-ext plugin that helps you describe the project settings in the build.gradle file.

  • correctly opening a project that contains both regular AppCode modules and Gradle modules.

  • accessing a project faster when you open it since AppCode reads the .iml files first and then starts the importing process.

Gradle projects

Automatically import this project on changes in build script files

If you select this checkbox, AppCode automatically re-imports your project every time you make changes in the build script files. In large projects, selecting this option might slow down the editing of your build script.

When you uncheck this option, you need to manually re-import the project every time you change build script files. In this case, you can control the re-importing of the project.

Build and run

Use this section to specify what AppCode should use when you run tests, build, or run tasks in the selected linked project.

Use Gradle from

Use this list to configure a Gradle version for your project.

You can select one of the following options:

  • '' file: this is a recommended default option that uses Gradle wrapper.

    In this case you delegate the update of Gradle versions to Gradle and get an automatic Gradle download for the build. This option also lets you build with a precise Gradle version. The Gradle version is saved in the file in the gradle directory of your project and helps you eliminate any Gradle version problems.

  • 'wrapper' task in Gradle build script: select this option to configure a Gradle wrapper according to the wrapper task configuration. It might be convenient if you prefer to control which Gradle version to use in the project.

    If you used the default Gradle wrapper option and then switched to the Gradle wrapper task configuration, changes you made in the task automatically update during the project import.

  • Specified location: select this option if you don't want to use the Gradle wrapper and prefer to manually download and use a specific Gradle version instead. Specify the location of your Gradle installation.

Gradle JVM

Use this field to specify the JVM under which AppCode will run Gradle when you import the specified Gradle project and when you execute its tasks. The default is set to your project JDK.

Last modified: 6 February 2020