In this chapter we have learned how to create our own enhanced task. We have seen how to add the class definition in our build file and use it directly in the build.

If we put the task definition in the buildSrc directory of a Gradle project or multi-project build, we can re-use the task in the context of the Gradle build. Also, we now have a good separation of the definition and configuration of the task.

Finally, we have learned how to publish the task as an artifact to a repository. Other projects can include the task in their classpath by using the buildscript{} script block. Then, we can configure and use the task in the project.

In this chapter we also learned how to write our own Gradle plugin. We have seen how to add a plugin class to our Gradle build file. Then we learned to use the buildSrc directory and place the source code of the plugin in there.

Finally, to make the plugin really reusable by other projects, we put the plugin code in a separate project. The plugin code is then packaged into a JAR file and published to a repository. Other projects can then define a dependency on the plugin and use the build logic from the plugin.

In the next chapter we see how we can use Gradle in continuous integration tools.