Gradle Plugins TODEPLETE: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
| Line 22: | Line 18: | ||
* [[Gradle IDEA Plugin|IDEA Plugin]] | * [[Gradle IDEA Plugin|IDEA Plugin]] | ||
* [[franzbecker gradle-lombok|franzbecker gradle-lombok]] | * [[franzbecker gradle-lombok|franzbecker gradle-lombok]] | ||
=Plugin Initialization= | =Plugin Initialization= | ||
Latest revision as of 21:54, 21 October 2020
Overview
Most of Gradle's power comes from external plugins. A plugin is an extension to Gradle which configures the project it is applied to in some way, typically by adding plugin-specific dependency configurations, tasks and properties. Plugins can be applied to Projects because Project implements PluginAware.
Plugin List
- Java Plugin
- Application Plugin
- Distribution Plugin
- War Plugin
- Maven Plugin
- Maven Publish Plugin
- ANTLR Plugin
- Spring Boot Plugin
- Spring dependency-management Plugin
- SonarQube Plugin
- Jacoco Plugin
- IDEA Plugin
- franzbecker gradle-lombok
Plugin Initialization
apply plugin:'java'
External Plugins
If a build requires external plugins that need to be downloaded dynamically, build.gradle allows for a special script block buildscript{...} to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with:
Plugin with id 'nebula.ospackage-application' not found.
An external plugin is declared as follows:
buildscript {
repositories {
maven { url 'https://plugins.gradle.org/m2/' }
}
dependencies {
classpath 'com.netflix.nebula:gradle-ospackage-plugin:4.3.0'
}
}
The plugin Script Block
What is this for? It seems to be the only way to apply some plugins:
plugins {
id "org.sonarqube" version "2.6"
}