Search Gradle plugins

com.gradle.plugin-publish

Owner: Gradle

Publish plugins to the Gradle Plugin Portal

https://plugins.gradle.org/docs/publish-plugin

Version 1.0.0-rc-2

Created 13 May 2022.

- Raise minimum supported Gradle version to 4.10.3
- Auto-apply `java-gradle-plugin` plugin
- Auto-apply `maven-publish` plugin (always used for publication metadata generation)
- Automate published artifact signing, if the `signing` plugin is applied
- Automatically publish the jar produced by the `shadowJar` task, as the main artifact, if the `com.github.johnrengelman.shadow` is applied (requires minimum Gradle version of 6.0.1)
- Remove `pluginBundle.plugins` block, use `gradlePlugin.plugins` instead
- Add `pluginBundle.pluginTags` map to enable per-plugin tags (for pre Gradle 7.5 versions, where `gradlePlugin.plugins` doesn't yet allow individual tags)
- Deprecate the entire `pluginBundle` block when using Gradle version 7.6 or later, mark for removal in version 8.0
- Remove `mavenCoordinates` block, use maven publication GAV instead
- Remove `withDependencies` block, set Java component dependencies instead
- Remove automatic Groovy docs generation

Kotlin
Groovy

Using the plugins DSL:

plugins {
  id("com.gradle.plugin-publish") version "1.0.0-rc-2"
}

Using legacy plugin application:

buildscript {
  repositories {
    maven {
      url = uri("https://plugins.gradle.org/m2/")
    }
  }
  dependencies {
    classpath("com.gradle.publish:plugin-publish-plugin:1.0.0-rc-2")
  }
}

apply(plugin = "com.gradle.plugin-publish")

Using the plugins DSL:

plugins {
  id "com.gradle.plugin-publish" version "1.0.0-rc-2"
}

Using legacy plugin application:

buildscript {
  repositories {
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  dependencies {
    classpath "com.gradle.publish:plugin-publish-plugin:1.0.0-rc-2"
  }
}

apply plugin: "com.gradle.plugin-publish"

Learn how to apply plugins to subprojects