Table of Contents
The IDEA plugin generates files that are used by IntelliJ IDEA, thus making it possible to open the project from IDEA (File - Open Project). Both external dependencies (including associated source and Javadoc files) and project dependencies are considered.
What exactly the IDEA plugin generates depends on which other plugins are used:
Table 68.1. IDEA plugin behavior
| Plugin | Description |
None |
Generates an IDEA module file. Also generates an IDEA project and workspace file if the project is the root project. |
Adds Java configuration to the module and project files. |
One focus of the IDEA plugin is to be open to customization. The plugin provides a standardized set of hooks for adding and removing content from the generated files.
To use the IDEA plugin, include this in your build script:
The IDEA plugin adds a number of tasks to your project. The main tasks that you will use are the idea and cleanIdea tasks.
The IDEA plugin adds the tasks shown below to a project. Notice that the clean task does not depend on the cleanIdeaWorkspace task. This is because the workspace typically contains a lot of user specific temporary data and it is not desirable to manipulate it outside IDEA.
Table 68.2. IDEA plugin - Tasks
| Task name | Depends on | Type | Description |
|
|
- |
Generates all IDEA configuration files |
|
|
Removes all IDEA configuration files |
|
|
- |
Removes the IDEA project file |
|
|
- |
Removes the IDEA module file |
|
|
- |
Removes the IDEA workspace file |
|
|
- |
Generates the |
|
|
- |
Generates the |
|
|
- |
Generates the |
Table 68.3. Configuration of the idea plugin
| Model | Reference name | Description |
|
Top level element that enables configuration of the idea plugin in a DSL-friendly fashion |
|
|
Allows configuring project information |
|
|
Allows configuring module information |
|
|
Allows configuring the workspace XML |
The IDEA plugin provides hooks and behavior for customizing the generated content. The workspace file can effectively only be manipulated via the withXml hook because its corresponding domain object is essentially empty.
The tasks recognize existing IDEA files, and merge them with the generated content.
Sections of existing IDEA files that are also the target of generated content will be amended or overwritten, depending on the particular section. The remaining sections will be left as-is.
To completely rewrite existing IDEA files, execute a clean task together with its corresponding generation task, like “gradle cleanIdea idea” (in that order). If you want to make this the default behavior, add “tasks.idea.dependsOn(cleanIdea)” to your build script. This makes it unnecessary to execute the clean task explicitly.
This strategy can also be used for individual files that the plugin would generate. For instance, this can be done for the “.iml” file with “gradle cleanIdeaModule ideaModule”.
The plugin provides objects modeling the sections of the metadata files that are generated by Gradle. The generation lifecycle is as follows:
The file is read; or a default version provided by Gradle is used if it does not exist
The beforeMerged hook is executed with a domain object representing the existing file
The existing content is merged with the configuration inferred from the Gradle build or defined explicitly in the eclipse DSL
The whenMerged hook is executed with a domain object representing contents of the file to be persisted
The withXml hook is executed with a raw representation of the XML that will be persisted
The final XML is persisted The following table lists the domain object used for each of the model types:
Table 68.4. Idea plugin hooks
| Model | beforeMerged { arg → } argument type |
whenMerged { arg → } argument type |
withXml { arg → } argument type |
A complete rewrite causes all existing content to be discarded, thereby losing any changes made directly in the IDE. The beforeMerged hook makes it possible to overwrite just certain parts of the existing content. The following example removes all existing dependencies from the Module domain object:
Example 68.2. Partial Rewrite for Module
build.gradle
idea.module.iml {
beforeMerged { module ->
module.dependencies.clear()
}
}
The resulting module file will only contain Gradle-generated dependency entries, but not any other dependency entries that may have been present in the original file. (In the case of dependency entries, this is also the default behavior.) Other sections of the module file will be either left as-is or merged. The same could be done for the module paths in the project file:
Example 68.3. Partial Rewrite for Project
build.gradle
idea.project.ipr {
beforeMerged { project ->
project.modulePaths.clear()
}
}
The whenMerged hook allows you to manipulate the fully populated domain objects. Often this is the preferred way to customize IDEA files. Here is how you would export all the dependencies of an IDEA module:
Example 68.4. Export Dependencies
build.gradle
idea.module.iml {
whenMerged { module ->
module.dependencies*.exported = true
}
}
The withXml hook allows you to manipulate the in-memory XML representation just before the file gets written to disk. Although Groovy’s XML support makes up for a lot, this approach is less convenient than manipulating the domain objects. In return, you get total control over the generated file, including sections not modeled by the domain objects.
Example 68.5. Customizing the XML
build.gradle
idea.project.ipr {
withXml { provider ->
provider.node.component
.find { it.@name == 'VcsDirectoryMappings' }
.mapping.@vcs = 'Git'
}
}
The paths of dependencies in the generated IDEA files are absolute. If you manually define a path variable pointing to the Gradle dependency cache, IDEA will automatically replace the absolute dependency paths with this path variable. you can configure this path variable via the “idea.pathVariables” property, so that it can do a proper merge without creating duplicates.