Book Image

Gradle Effective Implementations Guide - Second Edition

By : Hubert Klein Ikkink
Book Image

Gradle Effective Implementations Guide - Second Edition

By: Hubert Klein Ikkink

Overview of this book

Gradle is a project automation tool that has a wide range of applications. The basic aim of Gradle is to automate a wide variety of tasks performed by software developers, including compiling computer source code to binary code, packaging binary codes, running tests, deploying applications to production systems, and creating documentation. The book will start with the fundamentals of Gradle and introduce you to the tools that will be used in further chapters. You will learn to create and work with Gradle scripts and then see how to use Gradle to build your Java Projects. While building Java application, you will find out about other important topics such as dependency management, publishing artifacts, and integrating the application with other JVM languages such as Scala and Groovy. By the end of this book, you will be able to use Gradle in your daily development. Writing tasks, applying plugins, and creating build logic will be your second nature.
Table of Contents (18 chapters)
Gradle Effective Implementations Guide - Second Edition
About the Author
About the Reviewer

Using the IntelliJ IDEA plugin

IntelliJ IDEA from JetBrains is another IDE that we can use to develop applications. Gradle has the IDEA plugin to generate the project files for IntelliJ IDEA. This means that we can simply open the project in IntelliJ IDEA. The dependencies are set correctly to compile the project in the IDE. In this section, we will see how to generate these files and customize file generation.

IntelliJ IDEA supports a folder-based and file-based format for the project files. The IDEA plugin generates files for the file-based format. The file format for the project files is XML. The workspace project file has the .iws extension and contains personal settings. The project information is stored in a file with the .ipr extension. The project file can be saved in a version control system as it doesn't have a reference to local paths. The workspace project file has a lot of personal settings and this shouldn't be put in a version control system.

For a Java project, we have a third...