This proposal has been approved and the Eclipse Buildship: Eclipse Plug-ins for Gradle project has been created.
Visit the project page for the latest information and development.

Buildship: Eclipse Plug-ins for Gradle

Thursday, December 18, 2014 - 10:57 by Wayne Beaton
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project
Proposal State

Gradle is build automation evolved. Gradle can automate the building, testing, publishing, deployment and more of software packages or other types of projects such as generated static websites, generated documentation or indeed anything else.

Gradle combines the power and flexibility of Ant with the dependency management and conventions of Maven into a more effective way to build. Powered by a Groovy DSL and packed with innovation, Gradle provides a declarative way to describe all kinds of builds through sensible defaults. Gradle has become the build system of choice for many open source projects like Spring and Hibernate, leading edge enterprises like LinkedIn or Netflix and legacy automation challenges for some of the larget software stacks on the planet. The Gradle momentum is enormous with several millions of downloads in 2014.


Eclipse Plug-ins for Gradle provides Gradle developer tooling for Eclipse-based IDEs.


Eclipse Plug-ins for Gradle is a collection of Eclipse plug-ins that provide support for building software using Gradle.

Why Here?

Tight integration with Eclipse, especially the inclusion of Gradle support as a default feature in the standard Eclipse packages will draw the Eclipse and Gradle communities together for mutual benefit. There is also a lot of potential to extend the capabilities of Eclipse itself by a deeper integration with the build tool to provide a much more seamless and efficient developer experience. A good example for this are integration tests. When executed via the Eclipse test runner all the logic you have in your build to set up the test fixtures needs to be called manually before running the test via Eclipse. The alternative today is to run the tests directly via the build system without the visual goodness and usability of the Eclipse test runner. With Gradle we can integrate both approaches making Eclipse more powerful as a test execution engine.

Hans Docktor
Etienne Studer
Source Repository Type