Gradleware is the company behind Gradle. A build tool supporting Java, Scala, Groovy, Android, C/C++ and more.

Learn more about Gradleware's products and services.

Gradleware's approach is simple: we focus on efficiency. We make it easier for developers to write software by providing tools that address the complexity of today's applications.  

From builds that span both mobile platforms and server-side infrastructure, to builds that support cloud-based deployments across tens of thousands of nodes, to builds the involve every technology under the Sun - today's builds require a new approach.

Gradle: The Next Step

Gradleware is the company behind Gradle - the next-generation, open-source build system used in a variety of projects including Google's Android and the Spring Framework.   Gradleware offers training, services, and support for Gradle, and we employ the world's leading engineers with expertise in build systems and project automation.

Migrating to Gradle?   Moving an entire organization from one build system to another?  Our remote and on-site consultants can help you accelerate a migration or implement custom build requirements.   Here is a sample of some of the services offered by Gradleware Consulting:

At the core of our organization is an engineering team dedicated to the Gradle open source project.   If you need a custom feature implemented to support your unique requirements, our team of engineers can build and deliver custom Gradle distributions and custom Gradle plugins.   Gradleware can also prioritize the development of features in our open source offering based on your requirements.

  • Priority Open Source Development
  • Custom Gradle Distribution
  • Custom Gradle Plugins
  • Customized Tool Integration

Latest Activity

Creating a World-class C/C++ Build System in Gradle

Nov 11, 2013

The following video is the presentation that Adam Murdoch and Daz Deboer gave at Gradle Summit 2013 in Santa Clara, CA.  This presentation covers the developing support for native application development in Gradle.  At the end of this presentation, Adam provides several reasons for using Gradle for C++ and defines a set of features that are being planned for C++ support. 

Hans Dockter Talks Android at Twitter University

Oct 18, 2013

At JavaOne, I delivered an hour-long talk at Twitter headquarters in Downtown San Francisco.  This talk was a general discussion of the Android build system and the patterns used in that system and how we’re applying these patterns to other problems. If you are interested in hearing the latest about Gradle, here’s the video of my talk:

CARFAX at Gradle Summit 2013: An Agile Approach to Eliminating Technical Debt

Oct 15, 2013

As the vehicle history experts since 1986, CARFAX had amassed a sizable codebase spread across several teams comprised of both legacy systems and new initiatives alike.  Over many years, various technology, tools, and infrastructure had created an environment with a number of development environments.  At Gradle Summit 2013, Jim Noel, Director of Product Development at CARFAX, led a presentation from his team on an effort to migrate CARFAX builds to Gradle.  Here's the video of this presentation. Enjoy.

Watch Part One of the Gradle Workshop from Gradle Summit 2013

Oct 7, 2013

If you didn’t get a chance to make it to the Gradle Summit 2013, we’ve got the next best thing.  Peter Niederweiser conducted a 3-hour Gradle workshop in June that provides a great introduction to Gradle.  He led workshop attendees on a whirlwind tour of Gradle.  Showing both basics and some of the more interesting features about Gradle. Peter gives an overview of the Gradle project and starts from the foundations and motivations of the tool.  

Answering More Gradle v. Maven FUD

Jul 23, 2013
This post is a response to Sam Pullara’s “Why your new JVM build tool is making things worse.” I’m not interested in answering every post that pops up criticizing Gradle. People are entitled to their opinions, and Pullara is a capable engineer who has done good work at Twitter. My concern with this post is that I’m not convinced Pullara understands what Gradle is or how it works, so I wanted to take time to respond directly to some of his criticism.

Gradle's Momentum One Year After 1.0

Jun 22, 2013

It has been a little over a year since the release of Gradle 1.0.  In that timespan Gradle has had seven major releases.  Users have had to wait an average of 54 days between releases.  This is an average of 7.5 weeks - about a week over the target of a making release every six weeks.  I’ve seen how the project works, and Adam Murdoch guides the team toward a six week release cycle.

Observations from Gradle Summit 2013

Jun 19, 2013

Gradle Summit 2013 gave build engineers a place to collaborate and communicate. Sounds obvious, but it isn’t until you sit down for lunch at a conference like this and start hearing people’s stories about how Gradle is making a difference for these build engineers. When you choose a new tool, when you take on the task of rescuing some huge, problematic build, this task can be somewhat isolating. Few people in an organization understand the challenges of build automation and even fewer are willing to engage in such an effort.  

Get Started with Android and Gradle (in 9 Minutes)

May 23, 2013

Here's the thing, I know you are busy. I know you don't have an hour or two to spare to learn about a new tool and figure out how you are going to move your projects over to Gradle and Android Studio. That's why I took the time this week to make it easy to get started.