Hans Dockter

Hans Dockter

Founder of Gradle and CEO of Gradleware


Hans Dockter is the founder and project lead of the Gradle build system and the CEO of Gradleware, a company that provides training, support and consulting for Gradle and all forms of enterprise software project automation in general.

Hans has 13 years of experience as a software developer, team leader, architect, trainer, and technical mentor. Hans is a thought leader in the field of project automation and has successfully been in charge of numerous large-scale enterprise builds. He is also an advocate of Domain Driven Design, having taught classes and delivered presentations on this topic together with Eric Evans. In the earlier days, Hans was also a committer for the JBoss project and founded the JBoss-IDE.




Presentations

Gradle - the Innovation continues

The Gradle development team have not been taking it easy since the release of Gradle 1.0. New features and innovations are constantly being added, rough edges are being smoothed and the platform continues to expand. In this session we’ll explore the most notable additions to Gradle since the release of 1.0 and preview some of the new and exciting features just over the horizon with Gradle founder and Gradleware CEO Hans Dockter and Gradle core developer Peter Niederwieser.

Gradle continues to evolve with a high velocity to gain new capabilities, features and increased build performance.

We’ll dig into to some of the features incorporated since the 1.0 release, such as:

  • Maven import and archetype support
  • Parallel task execution
  • Improved Dependency Reporting
  • Dependency management improvements that make Grade the best dependency system out there.
  • Additions to the task model like soft dependencies and finalizer tasks.
  • Gradle Android and C/C++ Support
  • Improvements to the Tooling API (i.e. embedded Gradle)
  • Better scalability for large scale enterprise builds
  • Using Jenkins slaves for distributed test execution.
  • Deep integration with Arquillian for deploying to web and JEE servers.

We’ll also take a sneak peak at some of the upcoming features that will soon be available in Gradle.

The Art of Builds - An in-depth comparison of build tools

Discussions around Builds and Buildsystems haven't been treated for many years with the conceptual depth and principles they deserve and require. The lack of this is even more painful today as modern builds form a crucial part of a continuous delivery pipeline far away from the simple copy, compile and archive of the past. We will discuss the concepts of declarative and imperative builds, standardization of your build process, the executional model of a build system and dependency management. We will shed a lot of light into the dark with surprising results that are crucial to understand when deciding for a build system.

You will learn in this session :

  • What are declarative and imperative build and build systems? Followed by an in-depth discussion about advantages and dangers of their approaches.
  • Why Maven is more imperative than you might think.
  • The sweet spot in between standardization, declarativeness and necessary flexibility.
  • Gradle’s state of the art declarative approach shown by example of the new Gradle based Android build system.
  • Why and what it means that builds should focus as much on developer productivity as on enforcing the software factory.
  • Why also smaller projects should care about build system concepts (the larger ones don’t really have a choice.)
  • The importance of a rich execution model for build systems.
  • The problems with POM based dependency management and solutions to this.

This talk is driven by many examples from Gradle, Maven and Ant builds.