Previous | Next | See Also

This page displays the structure of a Gradle project, imported into IntelliJ IDEA. For each of the modules comprising the project, you can see its content root and dependencies (if any). The content roots are not editable.

Depending on the selected node, you can see the following settings:

Project

ItemDescription
NameThis field by default shows the name of the imported Gradle project. You can accept default, or change the project name as required.
Language levelSelect the Java language level to be supported. The selected level will be used as the project default.
The available options correspond to JSDK versions:
  • 1.3 - Plain old Java
  • 1.4 - 'assert' keyword
  • 5.0 - 'enum' keyword, autoboxing, etc.
  • 6.0 - @Override in interfaces
  • 7.0 - Diamonds, ARM, multi-catch, etc.
  • 8.0 - Lambdas, type annotations

An individual language level may be set for any of your modules.

SDKUse this group of controls to define the default SDK for the project.

You can define an individual SDK for each module.

Project config locationSpecify here the path to the directory, where .idea folder should reside. This field by default shows the project root directory, specified in the previous page.
Project compile output locationSpecify the path to the directory in which IntelliJ IDEA will store the compilation results. Click ellipsis button to select the directory in the Select Path dialog.
Two subdirectories in the specified directory will be created:
  • production for production code.
  • test for test sources.

In these subdirectories, individual output directories will be created for each of your modules.

The output paths may be redefined at module level.

Modules

ItemDescription
NameThis field by default shows the module name of the imported Gradle project. You can accept default, or change the module name as required.
Module file locationSpecify here the directory where *.iml file for the selected module will be stored. By default, this is the Project location directory.
Module config locationSpecify here the directory where *.iml file for the selected module will be stored. By default, this is the Project location directory.
Inherit project compile output pathClick this radio button to direct the compiler output to the path, configured on the project level.
Use module compile output pathClick this radio button to direct compiler output to the specified location:
  • Output path: specify the directory for the production classes.
  • Test output path: specify the directory for the test classes.
The following fields appear for the dependencies only.
ExportIf this check box is selected, a dependency is included in the compilation classpath of the dependent modules, as well as the classpath of the module which it is attached to.

If this check box in not selected, a dependency is only included in the compilation classpath of a module which it is attached to. Dependencies are always included in the runtime classpath regardless of the state of the Export check box.

ScopeUse this drop-down to affect the classpath for the various build phases.
  • Compile: This is the default option. If it is selected, the dependency is resolved and is available in classpath during the compilation and run phases.
  • Test: Select this option, if this dependency is only required for tests, and should not be available in normal application use. If this scope is selected, the dependency is resolved and is available in classpath during the test compilation and run phases.
  • Runtime: This scope indicates that the dependency is only required when running the application, and should not be available in classpath during the compilation.
  • Provided: If this option is selected, the dependency is resolved and is available in classpath during the compilation, but is not included in classpath at runtime. This dependency scope is useful, when you have some container that provides the dependency at runtime.

Content roots

The fields for the content roots are not editable. Use this pane to review the source, test and excluded roots.

See Also

Language and Framework-Specific Guidelines:

Reference:

Web Resources: