Explain how to create a Gradle plugin and its potential use cases.

Question

Accepted Answer

A Gradle plugin is a reusable unit of build logic packaged as a class that implements the Plugin interface. It encapsulates tasks, conventions, and configuration so teams can share build behavior across projects instead of copy-pasting build.gradle logic.

Key Points:
• A plugin class overrides apply(Project project) to register tasks, add extensions, or configure existing tasks.
• Plugins can be binary (compiled Java/Kotlin classes) or script plugins (separate .gradle files applied via apply from).
• Binary plugins are typically packaged as a JAR and published to a repository (Maven Central, an internal Nexus/Artifactory, or the Gradle Plugin Portal) for reuse.
• Custom extensions let a plugin expose a DSL block so consumers can configure it declaratively in build.gradle.
• Common use cases include enforcing company-wide code quality checks, standardizing versioning/release logic, and wrapping third-party tool integrations.

Example:
A platform team might build a "company-conventions" plugin that automatically applies Checkstyle, sets the Java toolchain version, and configures artifact publishing, so every microservice's build.gradle only needs one line: apply plugin: 'com.company.conventions'.

Code Example:
```
class GreetingPlugin implements Plugin {
    void apply(Project project) {
        project.task('hello') {
            doLast {
                println 'Hello from GreetingPlugin'
            }
        }
    }
}

apply plugin: GreetingPlugin
```

Interview Tip:
A concise interview answer is:

"A Gradle plugin implements Plugin and overrides apply() to register tasks or configuration; you package it as a JAR and publish it so other projects can reuse it via the plugins block. I've used custom plugins to enforce shared build conventions and automate repetitive setup like environment configuration across multiple microservices."