# Announcing Buildship 2.0

DevFeed: [Announcing Buildship 2.0](<https://devfeed.tech/articles/announcing-buildship-2-0-24594.md>)

Original publisher: [Read original article](<https://blog.gradle.org/announcing-buildship-2.0>)

Author: Donat Csikos

Published: 2017-01-11T05:00:00Z

Content type: release

Language: en

Sources: [The Gradle Blog](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [ide](<https://devfeed.tech/topics/ide.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [feature](<https://devfeed.tech/tags/feature.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [ide](<https://devfeed.tech/tags/ide.md>), [java](<https://devfeed.tech/tags/java.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [release](<https://devfeed.tech/tags/release.md>)

## AI overview

Gradle announces Buildship 2.0, its official Gradle support for Eclipse. The release adds composite build support, a redesigned UI, more accurate project synchronization, simpler project import, offline mode support, and an extension point for third-party integrators.

## Source excerpt

We are pleased to announce that version 2.0 of Buildship--our official Gradle support for Eclipse--is now available via the Eclipse Marketplace. This release adds support for composite builds, greatly reducing development turnaround time. The UI has been redesigned based on plenty of community feedback during the 1.x line. Project synchronization is now more accurate and project import requires one less step. We've added support for Gradle's offline mode (thanks Rodrigue!), and last but not least, third-party integrators can take advantage of our new InvocationCustomizer extension point. Read on for details about each of these new features. Composite build support What is a composite build? The composite build feature in Gradle allows you to handle several distinct Gradle builds as if they were one big multi-project build. This dramatically shortens the turnaround time when you need to work on several projects that are normally developed separately. Let's assume you have written a Java library lib, used by many of your applications. You find a bug which only manifests itself in the special-app. The traditional development workflow would be to change some code in lib and install a snapshot into the local repository. Then you would have to change the build script of special-app to use that new snapshot and check if the bug is actually fixed. With composite builds, however, you can tell Gradle to treat both of these projects as one. This will let special-app depend directly on the output of the lib project. You can learn more about composite builds in this introductory blog post. Composite builds in the IDE If you develop special-app you probably have it imported in Eclipse with lib referenced as a binary dependency. There is not much difference between working with composite builds at the command line and working with them within Eclipse. To include lib you need only add an entry to your settings.gradle file, telling Gradle from which folder the additional build should