Good news for all who use Gradle in their projects. The newest update of IntelliJ IDEA brings new features and enhancements for the Gradle integration.
Now IntelliJ IDEA provides you additional configuration settings:
- Use gradle wrapper — The IDE automatically detects if the linked gradle project is wrapper-aware and uses it for refreshing the project and running tasks;
- Use auto-import — Every project structure change is automatically picked up by the IDE on Gradle project refresh (e.g. when a new library is added/removed at build.gradle, it’s added/removed at the IDE as well). Note, that user-defined project changes are not automatically overwritten. E.g. when a user manually adds a library dependency to a module it’s not automatically removed during the auto-import.
- Service directory path — Allows to specify a location where Gradle stores downloaded library binaries. Useful for Windows’ users who may want to tune their anti-virus software.
Additionally to the new settings now you can use the new actions for managing Gradle project.
Now it’s possible to remove IDE’s local project entities easily from the Gradle tool window.
The outdated libraries are represented now as a single node. Before this change such libraries used to appear separately in ‘gradle-local’ and ‘ide-local’ nodes.
The next action allows you resolving the conflicts by applying Gradle’s values.
And the final new feature for Gradle in IntelliJ IDEA 12.1 is managing tasks. The list with tasks defined in the project is available on a new tab in Gradle tool window. With this new tab you can see recently executed tasks and run any of them by a double click or through the context menu.