Gradle Plugins TODEPLETE: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 25: Line 25:
=External Plugins=
=External Plugins=


If a build requires external plugins that need to be downloaded dynamically, [[build.gradle]] allows for a special script block [[Gradle_Project_and_Build_Script#buildscript.7B.7D|buildscript{...}]] to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with:
If a build requires external plugins that need to be downloaded dynamically, [[Gradle_Project_and_Build_Script#Overview|build.gradle]] allows for a special script block [[Gradle_Project_and_Build_Script#buildscript.7B.7D|buildscript{...}]] to declare where to download those plugins from. If the plugin is unknown, Gradle will fail with:


<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>

Revision as of 23:51, 19 May 2018

External

Internal

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 Initialization

apply plugin:'java'

Plugin List

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'
  }
}