Loading...

Composite Builds with Gradle and IntelliJ IDEA

1,294 views

Loading...

Loading...

Transcript

The interactive transcript could not be loaded.

Loading...

Loading...

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Mar 21, 2017

Composite Builds is a feature introduced in Gradle 3.1 to provide a way to decompose large multi-project builds into smaller, more isolated chunks that can be worked in independently or together as needed. When needed, binary dependencies are automatically replaced with project dependencies. When you make a change to an upstream component, it is immediately visible to its dependents.

Are you tired of publishing a library to your local repository just to check whether your change fixed that elusive bug in the application? Are you working on a mono-repo and wish you could import just a small part of it into your IDE? Would you like your projects to automatically react to other projects being checked out next to them? Then you should learn about Gradle's new Composite Build feature.

Since v2016.3 IntelliJ IDEA supports Composite Builds and allows you to work on them as if you were looking at a single code base. In IntelliJ IDEA 2017.1 this support is going to become even better.

Stefan Oehme (a core developer with Gradleware) and Trisha Gee (a developer advocate with JetBrains) will give you an overview of Composite Builds, the benefits of using them, and will show you how to work with them using IntelliJ IDEA.

Loading...

When autoplay is enabled, a suggested video will automatically play next.

Up next


to add this to Watch Later

Add to

Loading playlists...